> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/administration/managing-members.md).

# Managing members

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

## Workspaces and projects

Felt's [Workspaces and projects](/administration/workspaces-and-projects.md) allow organizations to manage their members, maps, and data in one place. Within a Workspace you can create Projects for different teams and/or work projects. These Projects keep your maps organized.

{% hint style="info" %}
Are you an educator? Check out [For classrooms](/administration/for-classrooms.md) on setting up your classroom in Felt!
{% endhint %}

## Creating your first workspace

After [signing up for Felt](https://felt.com/signup) you will be prompted to create a new workspace or join an existing one.

1. If your organization is not already using Felt, **create a workspace** by clicking on the **`Create a new workspace`** button:
2. **Name the workspace** after your organization.
3. **Invite your coworkers** by adding their emails. Click **`Send Invites`**. You can also add them later by clicking **`Invite members`** in Felt homepage.

## Workspace permissions

{% hint style="info" %}
For a comprehensive understanding of permissions in Felt, see [Permissions](/administration/felt-permissions.md).
{% endhint %}

You can invite teammates with one of two licenses:

<table data-header-hidden><thead><tr><th width="140"></th><th></th></tr></thead><tbody><tr><td><strong>Full seat</strong></td><td>Required to create maps, upload data, edit layers, contribute changes, or post comments. Counts toward your seat allotment. Professional includes 10 full seats; additional seats are $50/user/month.</td></tr><tr><td><strong>Viewer</strong></td><td>Unlimited. Can view maps they're shared with and read comments. Cannot post comments or edit.</td></tr></tbody></table>

For details on licenses and how they relate to permissions, see [Licenses](/administration/licenses.md).

#### Key things to know

* Only full-seat members can be granted Admin access in the account. Admins have full access to workspace settings, billing, and managing members.
* There must be at least one Admin in the account at all times.
* You can change a member's license at any time on the [members page](http://felt.com/maps/latest/members).
* Some permissions require features only available on Enterprise plans — see [Permissions](/administration/felt-permissions.md).

{% hint style="info" %}
Want a deeper dive on what each permission role can do? See [Permissions](/administration/felt-permissions.md).
{% endhint %}

### Managing member permissions

In the [members page](http://felt.com/maps/latest/members), you can invite new members, change member licenses, assign specific permissions, review member limits, or remove members from the workspace.

Licenses are managed the far right column and set the highest level permissions the member can have in the account. This column counts towards the workspace limits set in the account. Admin access is granted via this drop-down menu as well.

<figure><img src="/files/7kEWRc8dKl6lsdHqpsWC" alt="" width="237"><figcaption></figcaption></figure>

Permissions can be managed separately and can be applied specifically to a project, map, or data source in the Workspace. A member's permission on a specific resource can differ from the workspace default, but a viewer can never have more than View permission. This gives you flexibility to mix permission levels across your team — for example, a full-seat member can have Contribute permission on specific projects or View permission on specific maps.

<figure><img src="/files/aot6tnJUawBBXDBvSriE" alt="" width="375"><figcaption></figcaption></figure>

External collaborators who are only invited to specific maps, projects, or data sources will have no workspace-level permission. This means they will not be able to automatically view public projects or draft maps shared with other workspace members.

### Default permissions in Projects

To ensure members have access to the right maps, move maps into Projects in the workspace. Projects control which teammates have access to which maps, and Projects can be set to public (to everyone in the workspace) or private. Members in the same workspace can access maps in public projects and maps in private projects they're invited to.

The Project Admin can control member access and permissions on maps within a project using a default permission setting that is available within each Project's **`Share`** settings menu.

Within each public project, the Project Admin sets a default permission for all members with access to the project. The default permission for each project can be set as: View, Contribute, and Edit.

{% hint style="success" %}
To have every member have their same Workspace permissions in the project, set the default permission setting to Editor
{% endhint %}

This default permission overrides the members' workspaces permissions if the permission sets a lower access level than a member's workspace permission. But a default permission cannot grant a workspace member more permissions in a project than they have in the workspace.

For example, if a project's default permission setting is set to **View**, every member's permission will have view permission in that project:

* Any **full-seat member** will see the project maps as a **View**.
* Any **viewer** will see the project maps as a **View**.

<table><thead><tr><th width="180" align="center">Project Permission Setting</th><th width="220">Full-seat member</th><th>Viewer</th></tr></thead><tbody><tr><td align="center"><strong>View</strong></td><td>Project Viewer</td><td>Project Viewer</td></tr><tr><td align="center"><strong>Contribute</strong></td><td>Project Contributor</td><td>Project Viewer</td></tr><tr><td align="center"><mark style="color:$primary;"><strong>Edit</strong></mark></td><td>Project Editor</td><td>Project Viewer</td></tr></tbody></table>

#### For private projects

Only workspace members invited to the private project can see the maps in the project. When inviting a member to the private project, their permission level must match or be below the level set by their license (viewers are capped at View).

#### Invite external collaborators

You can also invite external collaborators or existing workspace members to specific projects and maps. External collaborators can only see maps they’ve been invited to.

## Manage email settings

To switch or change the email address for your account, navigate to <https://felt.com/users/settings>.

1. Click on your email address (you may be prompted to set a password first)
2. Enter your new email address
3. Click the confirmation link in the email sent to the new email address

{% hint style="info" %}
Felt treats certain email variations as duplicates to prevent multiple accounts.
{% endhint %}

## Removing a member

When you remove a member from the workspace, the following happens:

* The removed member is no longer able to login and access the workspace
* The removed member's Draft maps are transferred ownership to the admin who removed them
  * These drafts appear in a private project accessible to the admin
* Any private projects that are only accessible to the removed member are transferred ownership to the admin who removed them
* All maps created by the removed member transfer ownership to the admin who removed them
* All maps belonging to public projects and folders created by the removed member remain in their original place

## Organize your maps

**Create projects within the workspace to organize your maps** for different teams and/or work projects.

Create a new project by clicking **`+ Create Project`** when viewing your workspace

* **`Team visible`** projects can be seen and joined by anyone in the same workspace
* **`Private`** projects are invite-only and only seen by those invited

### Moving maps

You can **move maps or migrate maps to different projects in the workspace a few ways**

* When viewing a map:
  * Click on the current Project next to the map title → select the target Project
  * Click Felt menu → File → Move map...

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

* When viewing your workspace: click on the **`...`** → select move → select the target Project

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

{% hint style="info" %}
Maps can only be duplicated across workspaces. The original map will remain in the original workspace. Once duplicated to the new workspace you can delete the original map in the older workspace.
{% endhint %}

### Map folders

Within each project you can **create folders to organize maps within the same project**. You can create a new folder when viewing your project page. Folders can be nested.

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

## Organize your data

To learn more about managing your data with Felt, see [Data sources](/data-sources/data-sources.md).

Publish data to a **Felt Server** within your workspace so your teammates have access your organization's critical datasets. A Felt Server is a shared catalog of reusable map layers. Managing datasets in a Felt Server means every new map gets the same data styled the same way, without repeat uploads.

For more information, see [Felt Servers](/data-sources/felt-servers.md).


---

# 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:

```
GET https://help.felt.com/administration/managing-members.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.