For the complete documentation index, see llms.txt. This page is also available as Markdown.

Permissions

Understand View, Contribute, Edit, and Admin access in Felt. Learn how permissions work across maps, projects, data sources, and workspaces.

A seat lets someone work in Felt; access levels control what they can do on each map, project, data source, and workspace. In ArcGIS terms, a seat is closest to a user type, and access levels replace roles. Admin, Edit, and Contribute access need a seat. View access doesn't. See Seats and viewers.

Object
Access levels

Map

View, Contribute, Edit

Project

View, Contribute, Edit, Project admin

Data source

View, Edit, Source admin

Workspace

View, Contribute, Edit, Admin, None

To give access, see Manage members and Share a map.

Map-level permissions

Action
View
Contribute
Edit

Open the map, search, and turn layers on and off for yourself

Yes

Yes

Yes

Open layer tables

When allowed

When allowed

Yes

Read and post comments

Yes

Yes

Yes

Export the map as an image or PDF

Yes

Yes

Yes

Export layer data

When allowed

When allowed

Yes

Duplicate the map

When allowed

When allowed

Yes

Draw, edit, and delete annotations

No

Yes

Yes

Add, edit, and delete features and their attribute values, including photos

No

Yes

Yes

Capture field data in the Field App

No

Yes

Yes

Upload data, and add, style, and delete layers

No

No

Yes

Add and remove table columns

No

No

Yes

Run spatial analysis and SQL queries

No

No

Yes

Rename the map, change map settings, and add dashboard components

No

No

Yes

Export annotations, and delete or resolve anyone's comments

No

No

Yes

Invite people, change their access, and change public link access

No

No

Yes

"When allowed" depends on the map settings: Viewers can open table and Duplicate map and data are on by default, and Export data is off by default. In those settings, "viewers" means people without Edit access to the map. Duplicating creates a new map, so it also needs a seat in the workspace you copy the map into. Editing layer data and exporting also depend on your plan.

Deleting a map needs Edit access to its project, or the map must be in your drafts. Edit access to the map alone isn't enough.

People with Contribute or Edit access see each other's live cursors while they edit the map, and in view mode too when the See map presence map setting is on. That setting also shows everyone the avatars of others on the map. People with View access, people on a public link, and embedded maps don't show live cursors.

To change a map, click Edit map in the toolbar, or Contribute if you have Contribute access. With View access, neither appears. Ask someone with Edit access to the map, or a workspace admin, for a higher access level.

Editing a Felt Server layer also needs Edit access to that Felt Server.

Limit what each person can see

Everyone with access to a map can see all its layers, features, and rows. To limit who sees which data, put it on separate maps and share each map or project with the right people. Database queries use the source's credentials, not those of the person viewing the map.

Project-level permissions

Project access applies to every map in the project, and Project admin gives Edit access to the maps.

Action
View
Contribute
Edit
Project admin

See the project and open its maps

Yes

Yes

Yes

Yes

Create, delete, and move maps, and manage folders

No

No

Yes

Yes

Rename the project

No

No

Yes

Yes

Invite people and change their access, other than Project admins

No

No

Yes

Yes

Invite Project admins and change their access

No

No

No

Yes

Change the project's icon, visibility, and workspace default

No

No

No

Yes

Delete the project

No

No

No

Yes

To move a map, you need Edit access to both projects.

Workspace-level permissions

Workspace access sets what a member can do across the workspace, including projects and data sources open to it. External collaborators have no workspace access (None).

In the Seat type column on the Members tab, Seat gives Edit access to the workspace, and Viewer gives View access.

Action
Admin
Edit
Contribute
View
None

See the member list and the projects open to the workspace

Yes

Yes

Yes

Yes

No

Create maps

Yes

Yes

Yes

No

No

Create projects

Yes

Yes

No

No

No

Add data sources, including Felt Servers

Yes

Yes

No

No

No

Create and delete your own API tokens, manage your own webhooks, and connect MCP

Yes

Yes

No

No

No

Upload custom icons

Yes

Yes

No

No

No

Invite and remove members, and change their access

Yes

No

No

No

No

Change workspace settings, and see usage and billing

Yes

No

No

No

No

Delete the workspace

Yes

No

No

No

No

Anyone with a seat can create maps, including people with Contribute access to the workspace. New maps start in your drafts unless you create them inside a project.

A workspace always has at least one admin. The only admin can't leave the workspace or remove their own Admin access. Each person's API tokens are their own: no one else, including an admin, can delete them.

Workspace admins can't open private projects or maps they haven't been invited to, but they can change anyone's access on the Members tab.

Data source-level permissions

Workspace members inherit access to a source, capped by its workspace default: None, View, or Edit. The default starts at View. Within that cap, Admin or Edit workspace access gives Edit access to the source; Contribute or View gives View. With a default of None, only people invited to the source can use it.

Action
View
Edit
Source admin

See the source, browse its data, and add its layers to a map

Yes

Yes

Yes

Write SQL queries against the source

No

Yes

Yes

Edit, rename, or delete the source

No

Yes

Yes

Publish, organize, and delete layers in a Felt Server

No

Yes

Yes

Invite people and change their access, other than Source admins

No

Yes

Yes

Invite Source admins, and change the workspace default

No

No

Yes

Invite people to a data source

Invite people from the source's share menu. See Data sources.

How access is inherited

Map access can come from an invitation, the map's project, the workspace, or a public link. The highest access level applies. Drafts also follow Enterprise workspace sharing defaults. See Organize maps.

A project set to Workspace is open to the workspace. Each member inherits their workspace access, capped by the project's workspace default. To give someone a higher access level, invite them to the project. A private project is open only to people invited to it.

Workspace access
Default: View
Default: Contribute
Default: Edit

Admin or Edit

View

Contribute

Edit

Contribute

View

Contribute

Contribute

View

View

View

View

None

No access

No access

No access

Last updated

Was this helpful?