Permissions

Reference page listing out all permissions per role

Introduction to permissions

Anyone invited to a Felt workspace is considered a member of that workspace. Every member has a seat (set at the workspace level) and a permission role on each project, map, or data source they have access to. For details on the seat model, see Seats.

Felt permissions can be broken out into the following categories:

• Workspace settings: Managing the workspace, members, and billing

• Project-level settings: Creating and managing projects and folders

• Map settings: Viewing and editing map content

• Map management: Managing map access and permissions

• Data source settings: Managing access to and contents of Felt Servers, Cloud sources, and Raster infrastructure sources

This page outlines which seat and permission roles have access to features according to these categories.

Key things to know

• Only members with a Full Access seat can be granted Admin access. Admins have full access to workspace settings, billing, and managing members.

• There must be at least one Admin in the workspace at all times.

• You can rotate or swap seats across members in the workspace when managing members.

• Some permissions (marked enterprise below) require features that are only available on Enterprise plans.

Seats vs permissions

The seat type sets the ceiling on what a member can do in the workspace. Permissions determine what they can do on a specific project, map, or data source.

In the members page, seats are managed in the far-right column. This column counts toward the seat allotment in your plan. Admin access is granted via this dropdown menu as well.

Permissions are managed separately and can be specific to a project, a map, or a data source in the workspace. For example: a member with a Full Access seat can have Contribute permission on specific projects, View permission on specific maps, and Source admin / Edit / View on specific Felt Servers, Cloud sources, or Raster infrastructure sources.

---

Workspace-level permissions

The permission tables below describe what each permission role (View, Contribute, Edit, Admin) can do at the workspace, project, map, and data source level. A Full Access seat can be granted any permission role; a Viewer seat is capped at View.

Permission	View	Contribute	Edit	Admin
Leave workspace	✅	✅	✅	✅
Create a Felt Server	❌	❌	✅	✅
Connect a Cloud or Raster source	❌	❌	✅	✅
Publish to a Felt Server (where granted Edit+)	❌	❌	✅	✅
Create projects	❌	❌	✅	✅
Create/remove API tokens	❌	❌	✅	✅
See layer limit warnings	❌	❌	✅	✅
See payment failure warnings	❌	❌	✅	✅
Delete workspace	❌	❌	❌	✅
Rename workspace	❌	❌	❌	✅
Invite members	❌	❌	❌	✅
Remove members	❌	❌	❌	✅
Adjust member permissions	❌	❌	❌	✅
Manage billing/payments	❌	❌	❌	✅
View usage dashboard	❌	❌	❌	✅

Whether a member can see a particular data source in the library is governed per-source, not at the workspace level. See Data source-level permissions below.

Project-level permissions

Assumes project access is granted.

Permission	View	Contribute	Edit	Admin
View maps in project	✅	✅	✅	✅
Create maps	❌	❌	✅	✅
Delete maps	❌	❌	✅	✅
Move maps in/out of project	❌	❌	✅	✅
Create/rename/delete folders	❌	❌	✅	✅
Invite or remove non-admin members	❌	❌	✅	✅
Adjust non-admin member permissions	❌	❌	✅	✅
Rename the project	❌	❌	✅	✅
Invite or remove project admins	❌	❌	❌	✅
Change project visibility	❌	❌	❌	✅
Change the workspace-default access	❌	❌	❌	✅
Delete the project	❌	❌	❌	✅

Map-level permissions

Map viewing permissions	View	Contribute	Edit
Read comments	✅	✅	✅
Post comments (requires Full Access seat)	✅	✅	✅
Search	✅	✅	✅
See live presence	✅	✅	✅
See live cursors	✅	✅	✅
View maps	✅	✅	✅
View table	✅	✅	✅
Toggle legend layers (for self)	✅	✅	✅
Attach photos to comments	❌	✅	✅

The columns above describe what each permission level can do. Viewer-seat members (without a Full Access seat) are capped at View — they can read maps and read comments, but cannot post comments or edit.

Map editing & data management	View	Contribute	Edit
Add/edit annotations	❌	✅	✅
Add images as annotations	❌	✅	✅
Attach photos to annotations	❌	✅	✅
Add/edit/delete data in layers	❌	✅	✅
Attach photos to features	❌	✅	✅
Create new layers from scratch	❌	❌	✅
Connect to data sources (Cloud Sources are Enterprise)	❌	❌	✅
Delete map	❌	❌	✅
Delete layers	❌	❌	✅
Duplicate map	❌	❌	✅
Export data	*See note	*See note	✅
Publish to a Felt Server (requires Edit or Source admin on the server)	❌	❌	✅
Rename map	❌	❌	✅
Set default layer visibility	❌	❌	✅
Spatial analysis	❌	❌	✅
Upload data	❌	❌	✅

*Note: By default, members with View or Contribute permission cannot export data from a map. They can export if the setting is enabled by an editor or admin in the map settings.

Map management

Permission	View	Contribute	Edit
Adjust individual permissions	❌	❌	✅
Adjust public access settings	❌	❌	✅
Configure viewer permissions	❌	❌	✅
Invite members to map	❌	❌	✅
Remove individuals from map	❌	❌	✅

Data source-level permissions

Felt Servers, Cloud sources, and Raster infrastructure sources have their own permissions, separate from the workspace seat. A member's role on a specific source is assigned via the Share dialog on that source — see Sharing a data source for the sharing workflow. The three roles are Source admin, Edit, and View.

The Global Library is visible to every workspace and has no per-source permissions.

Permission	View	Edit	Source admin
See layers from this source on a map	✅	✅	✅
See the source in the library	✅	✅	✅
Add a layer to a map	✅	✅	✅
Create folders in a Felt Server	❌	✅	✅
Publish a layer to a Felt Server	❌	✅	✅
Invite or remove non-admin members	❌	✅	✅
Edit connection details	❌	✅	✅
Delete or rename the source	❌	✅	✅
Invite or remove Source admins	❌	❌	✅
Change the workspace-default access	❌	❌	✅