Felt 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. Members can have one of three licenses:
Viewer
Someone who can only view the workspace, project, or map. They can leave comments on maps for free but they will not see the Felt toolbar when viewing the map
Contributor
Someone who can edit data on maps where they're granted access, but cannot create new maps or upload data
Editor
Someone with permissions to create and manage maps or data in the workspace (can create new maps and upload data)
The Contributor license is only available to Enterprise plans. Free and Team plans have access to the Viewer and Editor licenses.
Key things to know
Only Editors 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 rotate or swap licenses across members in the workspace when managing members.
Permissions using Enterprise features are specified below.
Licenses vs permissions
Licenses set the maximum permission a member can have in the Workspace, while permissions determine what a member can do in the workspace, on a specific projects, or for individual maps.
In the members page, 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.
Permissions are managed separately and can be specific to a project or map in the Workspace. For example: an editor in the workspace can have contributor or viewer permissions on specific projects and maps.
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
This page outlines which license has access to permissions according to these categories.
Workspace-level permissions
Leave workspace
✅
✅
✅
✅
Add/remove layers from library
❌
❌
✅
✅
Create projects
❌
❌
✅
✅
Create/remove API tokens
❌
❌
✅
✅
See layer limit warnings
❌
❌
✅
✅
See payment failure warnings
❌
❌
✅
✅
View layer library
❌
❌
✅
✅
Delete workspace
❌
❌
❌
✅
Rename workspace
❌
❌
❌
✅
Invite members
❌
❌
❌
✅
Remove members
❌
❌
❌
✅
Adjust member permissions
❌
❌
❌
✅
Manage billing/payments
❌
❌
❌
✅
View usage dashboard
❌
❌
❌
✅
Project-level permissions
Assumes project access is granted.
View maps in project
✅
✅
✅
Add members to project
❌
❌
✅
Adjust member permissions
❌
❌
✅
Create maps
❌
❌
✅
Create/rename/delete folders
❌
❌
✅
Delete maps
❌
❌
✅
Move maps in/out of project
❌
❌
✅
Remove members from project
❌
❌
✅
Map-level permissions
Comment
✅
✅
✅
Search
✅
✅
✅
See live presence
✅
✅
✅
See live cursors
✅
✅
✅
View maps
✅
✅
✅
View table
✅
✅
✅
Toggle legend layers (for self)
✅
✅
✅
Attach photos to comments (enterprise)
❌
✅
✅
Add/edit annotations
❌
✅
✅
Add images as annotations
❌
✅
✅
Attach photos to annotations
❌
✅
✅
Add/edit/delete data in layers (enterprise)
❌
✅
✅
Attach photos to features (enterprise)
❌
✅
✅
Create new layers from scratch (enterprise)
❌
❌
✅
Connect to data sources (enterprise)
❌
❌
✅
Delete map
❌
❌
✅
Delete layers
❌
❌
✅
Duplicate map
❌
❌
✅
Export data
*See note
*See note
✅
Publish to layer library (enterprise)
❌
❌
✅
Rename map
❌
❌
✅
Set default layer visibility
❌
❌
✅
Spatial analysis
❌
❌
✅
Upload data
❌
❌
✅
*Note: By default, Viewers and Contributors cannot export data from a map. But Viewers and Contributors can export data from a map if the setting is enabled by an editor or admin in the map settings.
Map management
Adjust individual permissions
❌
❌
✅
Adjust public access settings
❌
❌
✅
Configure viewer permissions
❌
❌
✅
Invite members to map
❌
❌
✅
Remove individuals from map
❌
❌
✅
Last updated
Was this helpful?