# Creating a Group/Project

### Overview

Workspaces in MangoApps help organize employees based on their functions and collaboration needs within a company. Creating a workspace provides a structured environment for smooth communication and efficient teamwork.

<figure><img src="/files/u1rWClRfLODDhP0onmVc" alt="" width="563"><figcaption></figcaption></figure>

Creating a workspace consists of 3 steps: **Enter Details**, **Configure Modules**, and **Set Custom Fields**.

***

### Enter Details

In this section, admins will define the workspace details.

* **Name (Required):** Enter a unique name that clearly identifies the workspace.

{% hint style="info" %}
Groups and Projects can be renamed at anytime after creation
{% endhint %}

* **Short Description:** Provide a concise summary of the workspace's purpose (limit: 2,000 characters).
* **Upload a Photo (Optional):** Add a logo or relevant image (250x250 px, <100KB). To exclude an image, uncheck the **Show Photo** box.
* **Banner:** Select a banner to display at the top of the workspace. This banner also appears on the workspace card when viewed in card view. The banner will span the full width within projects, groups, and departments. The recommended banner size remains 1920 × 150 px.
* **User can Hide Banner**: Select this option to allow users to hide the banner message upon logging in. Any changes made to the banner afterward will cause it to reappear the next time users log in.
* **Assign Categories:** Choose relevant categories to help users easily find the workspace.

#### **Set Workspace Permissions**

* **Public:** Anyone can view the content and participate in the work space. Also, these users can join the space to see updates on their News Feed.
* **Private:** Only workspace members can view and interact with content.
  * **Allow Non-Members to Post Updates:** Check this box to allow non-members to post updates in the workspace. Non-members can view their own updates and receive notifications for comments on their updates but cannot see updates they did not post.
* **Unlisted:** Only invited users can view the workspace. Network Admins **do not** have access by default.

#### **Set Default Membership Roles**

* **Member:** Users can participate and view content.
* **Admin:** Users can manage workspace settings and permissions.

#### **Assign Hashtags**

* Add relevant hashtags to improve searchability of the workspace.

#### **Additional Configurations (Projects Only)**

* **Set Start and Completion Dates:** Define project timelines.
* **Choose a Time Zone:** Ensure deadlines align with team locations.
* **Color:** Select a color to represent the project on the project calendar.

***

### Group/Project Templates

Admins can create workspace templates for users within a domain to ensure consistency, efficiency, and ease of use. A couple reasons admins may want to use templates are:

* **Standardization** – Templates help enforce best practices, ensuring all users follow a consistent structure for projects, reducing confusion and inefficiencies.
* **Time-Saving** – Instead of starting from scratch, users can quickly set up projects with pre-configured settings, tools, and structures tailored to their needs.
* **Scalability** – As teams grow, standardized templates make it easier to onboard new users and ensure they adhere to organizational workflows without extensive training.
* **Compliance & Governance** – Ensures that all projects adhere to company policies, industry regulations, or legal requirements.

For information on creating workspace templates, check out the Admin Portal guides for [**Project Templates**](https://guides.mangoapps.com/admin-guide/module-settings/projects/project-templates) and [**Group Templates**](https://guides.mangoapps.com/admin-guide/module-settings/groups/group-templates).

#### Ownership Rules for Templates

When creating a group from a template, the creator can decide whether the new space is owned by:

* **The template creator** (default): Template creator becomes admin, current creator is not added.
* **Themselves (the creator)**: Current creator becomes admin, template owner is not added.

***

### Configure Modules

In this step, admins can add modules to the workspace and configure the module behavior for the space. When enabled, these modules will appear along the left hand side of the workspace.&#x20;

<figure><img src="/files/x3Yv9irfIbRKCnAsqWgD" alt="" width="563"><figcaption></figcaption></figure>

Admins for the workspace can re-arrange the module order by clicking and dragging the modules up and down the list. Each module can also be renamed to suit company purposes.

<figure><img src="/files/zLeiXW3pWljcVahPweZq" alt="" width="563"><figcaption></figcaption></figure>

Modules can be enabled or disabled at any time from the [Admin Tools](https://guides.mangoapps.com/user-guide/workspaces/workspace-toolbars#edit-workspace-and-module-details) menu within the workspace.

{% hint style="info" %}
If you would like to have no side navigation for your workspace, click **Settings** next to each module and toggle the **Show in Navigation** option to **OFF**. The workspace photo can also be disabled to completely remove the left hand panel from the workspace.

Admins for the workspace can still access these modules via the **View Modules** option in the **Admin** dropdown menu.
{% endhint %}

<figure><img src="/files/b75w1gRW9AYgKQKWxuLv" alt=""><figcaption></figcaption></figure>

***

### Set Custom Fields

In this last step, admins have the option to provide additional details about the workspace using custom fields. These custom fields can be configured by admins within the [Admin Portal> Modules > Groups (or Projects)](https://guides.mangoapps.com/admin-guide/module-settings/groups#managing-group-settings).

Custom fields will appear within the **Group/Project Summary** on the right hand side of the News Feed module within the workspace.&#x20;

<figure><img src="/files/9Ir33OUrizc8ZxoX5J0J" alt="" width="563"><figcaption></figcaption></figure>

While this step is not required, filling out these details can enhance organization, improve searchability, and provide team members with useful context about the workspace’s purpose and contents.

Some **use case examples** for setting **custom fields** include:

**Project Management-** Project Owner, Deadline, Priority Level

**Client-Specific Workspaces-** Client Name, Contract Expiration Date, Industry

**Knowledge-Sharing Communities:** Focus Area, Key Contributors, Knowledge Base Link

**Volunteer Groups:** Cause/Initiative, Volunteer Opportunities, Partner Organizations

**HR & Recruiting-** Job Position, Hiring Manager, Application Deadline


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guides.mangoapps.com/user-guide/groups-and-projects/creating-a-group-project.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.