> For the complete documentation index, see [llms.txt](https://biggeo.gitbook.io/biggeo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://biggeo.gitbook.io/biggeo/biggeo-studio/permissions/overview.md).

# Overview

In BigGeo Studio, **Permissions** allow administrators to control and customize access levels for each user. BigGeo Studio provides a flexible, area-based permissions system, enabling you to assign different roles to team members in specific areas of the platform, such as Datascape, Datalab, or Velocity. This ensures that each team member has the appropriate level of access based on their role and responsibilities within the organization.

***

## How Permissions Work

Permissions in BigGeo Studio are assigned at the **area level**. This means that you can set different access levels for each product space and management area independently, giving you full control over who can view, edit, or manage specific parts of the platform.

Key components of the BigGeo Studio permissions system include:

* **Area-Based Access**: Permissions are set individually for each area, allowing team members to have varied access levels in different sections of BigGeo Studio.
* **Roles**: BigGeo Studio has two main roles—**Admin** and **Standard**—each with specific access capabilities.

***

## Roles and Access Levels

BigGeo Studio defines two roles for each area, allowing you to customize access as needed:

* **Admin**:
  * Admins have full control over the areas they are assigned to.
  * They can create, edit, and manage content, add or remove team members, and adjust settings within their designated areas.
  * This role is suitable for team leaders, project managers, or any users who need comprehensive control over a particular product space or function.
* **Standard**:
  * Standard users have limited, view-only access within the areas they are assigned to.
  * They can monitor content and view data but cannot create, edit, or manage settings.
  * This role is ideal for team members who need to access information without making changes.

***

## Key Features of the Permissions System

* **Area-Based Permissions**: Assign different roles for each area in BigGeo Studio. For example, a user can be an Admin in Datascape but have Standard access in Settings, allowing for flexible role assignments based on specific responsibilities.
* **Granular Control**: By setting permissions at the area level, BigGeo Studio lets you control exactly what each team member can see and do, reducing the risk of unauthorized changes or access to sensitive data.
* **Role Customization for Different Product Spaces**: Assign Admin or Standard roles for each product space (Datascape, Datalab, Velocity, etc.) and management functions (Marketplace, Team Management, Settings), allowing for detailed access configurations.

***

## Managing Permissions

To manage permissions for team members in BigGeo Studio:

1. **Navigate to the My Team Section**: In BigGeo Studio, go to **My Team** in the sidebar.
2. **Select a Team Member**: Click **Manage** next to the team member whose permissions you want to adjust.
3. **Assign Permissions**: In the permissions section, set the member’s role as either **Admin** or **Standard** for each area. This customizes their access to specific functions within BigGeo Studio.
4. **Save Changes**: Once you have assigned the necessary roles, click **Save Changes** to update the permissions.

***

## FAQs

<details>

<summary><strong>Can a team member have different roles in different areas?</strong></summary>

Yes, BigGeo Studio supports area-based permissions, allowing you to assign Admin access in one area (e.g., Datalab) and Standard access in another (e.g., Settings), based on the member’s responsibilities.

</details>

<details>

<summary><strong>How do permissions affect team access to product spaces?</strong></summary>

Permissions determine what actions a team member can perform within each product space. For example, Admins in Datascape can create and manage datasets, while Standard users can only view datasets.

</details>

<details>

<summary><strong>Can I update permissions after initially assigning them?</strong></summary>

Yes, you can adjust a team member’s permissions at any time by navigating to the My Team section and managing their profile.

</details>

<details>

<summary><strong>Are permissions affected by team assignments?</strong></summary>

No, team assignments are for organizational purposes only and do not impact permissions. Each team member’s access is defined individually in the permissions settings.

</details>

***

BigGeo Studio’s permissions system offers flexibility and control, ensuring that each team member has the appropriate level of access for their role. For additional guidance, explore our articles on **Adding a Team Member** and **Managing Team Member Permissions**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://biggeo.gitbook.io/biggeo/biggeo-studio/permissions/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
