> 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/team-members/overview.md).

# Overview

Welcome to the **Team Members** section in BigGeo Studio, your central hub for managing access, roles, and permissions across your organization’s BigGeo product spaces. BigGeo Studio offers area-based permissions, allowing you to customize each team member’s role by specific areas within product spaces like Datascape and Datalab, ensuring that access is tailored precisely to their responsibilities.

***

## What is the Team Members Section

The **Team Members** section in BigGeo Studio allows administrators to manage all users associated with their organization. By adding team members, assigning them area-based roles, and controlling permissions, organizations can ensure that each user has appropriate access to sensitive data and tools within specific product spaces.

In this section, you can:

* **Add New Team Members**: Invite users to join your organization and assign access to specific product spaces.
* **Assign Area-Based Roles and Permissions**: Define each member’s level of access in different areas of a product space, allowing for Admin rights in one area and Standard in another.
* **Monitor Team Activity**: Track user activity across product spaces to maintain security and accountability.

***

## Key Features of Team Management

* **Centralized Team Management**: Manage all team members and permissions from a single, organized interface within BigGeo Studio.
* **Area-Based Role Customization**: Assign area-based permissions within each product space, granting different levels of access based on team members’ responsibilities.
* **Cross-Product Access**: Control team member access across BigGeo products, such as Datascape, Datalab, and Velocity, from one centralized location.
* **Scalability for Organizations of All Sizes**: Whether your organization has a few team members or hundreds, BigGeo Studio’s team management system is built to scale efficiently.

***

## Getting Started with Team Members

To get started with team management in BigGeo Studio, follow these basic steps:

1. **Add a Team Member**:
   * Navigate to the **Team Members** section and click **Add New Member**.
   * Enter the user’s email address to send them an invitation to join your organization in BigGeo Studio.
2. **Assign Area-Based Roles and Permissions**:
   * Once the new member has accepted the invitation, assign them roles within each area of a product space as needed.
   * For example, a team member could have **Admin** access in specific areas, such as Dataset Management in Datascape, and **Standard** access in other areas, like Visualization.
3. **Monitor Activity and Manage Permissions**:
   * Use the Team Members section to adjust area-specific permissions or remove users as your organization’s needs change.
   * Regularly review user roles and area-based access to maintain data security.

***

## Roles and Permissions

BigGeo Studio offers two main roles with area-based customization:

* **Admin**:
  * Full access within designated areas, including the ability to create, edit, and manage data and settings.
  * Can also manage team members and permissions within the areas assigned to them.
  * Ideal for team leaders or project managers who need oversight of specific areas within a product space.
* **Standard**:
  * Limited access, typically restricted to viewing or monitoring specific areas.
  * Cannot create, edit, or manage content in their assigned areas.
  * Suitable for team members who need access to data without modifying it.

{% hint style="info" %}
**Note**: Area-based permissions enable users to have Admin rights in one area and Standard rights in another, tailoring access precisely to their responsibilities.
{% endhint %}

***

## FAQs

<details>

<summary><strong>Can I assign different roles to a team member in different areas of a product space?</strong></summary>

Yes, area-based permissions allow you to grant **Admin** rights in certain areas (e.g., Dataset Management) while assigning **Standard** rights in others (e.g., Visualization). This ensures team members have the exact level of access needed.

</details>

<details>

<summary><strong>Can I update a team member’s area-based roles after they’ve been added?</strong></summary>

Absolutely! You can adjust each member's area-based roles and permissions at any time from the Team Members section.

</details>

<details>

<summary><strong>How can I remove a team member from the organization?</strong></summary>

To remove a team member, go to the Team Members section, find the user, and select the option to remove them. This will revoke their access to all product spaces and areas.

</details>

<details>

<summary><strong>Will team members be notified if their permissions are changed?</strong></summary>

Yes, team members receive notifications whenever there is a change to their area-specific permissions or access levels within BigGeo Studio.

</details>

***

The **Team Members** section in BigGeo Studio makes it easy to customize user access and maintain security across your organization’s product spaces. For further guidance, see our help articles on **Adding a Team Member** and **Managing Area-Based Permissions for Team Members**.


---

# 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/team-members/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.
