Organization Member
unless specified. For example, if I invite someone to a project as an editor, they will become an organization member with editor
access to that project. If I invite someone to the organization as a viewer
, then they will be an organization viewer
(instead of an organization member
).
Action | Project Admin | Project Developer | Project Editor | Project Interactive Viewer | Project Viewer |
---|---|---|---|---|---|
View charts and dashboards | |||||
Export visible results to CSV | |||||
Export visible results to Google Sheets | |||||
Export all results to CSV (override the visible limit) | |||||
Export all results to Google Sheets (override the limit) | |||||
View comments | |||||
Create comments | |||||
Create new query from tables explore | |||||
View underlying data | |||||
Create and edit scheduled deliveries | |||||
Create and edit Syncs | |||||
Create and edit charts and dashboards | |||||
Use the SQL runner | |||||
Create and explore custom SQL dimensions | |||||
Create virtual views | |||||
Manage project access and permissions | |||||
Delete project | |||||
Create a preview project | |||||
Use dashboards as code (CLI) | |||||
Rename models, dimensions, and metrics (CLI and UI) |
Action | Organization Admin | Organization Developer | Organization Editor | Organization Interactive Viewer | Organization Viewer | Organization Member |
---|---|---|---|---|---|---|
Create Personal access tokens | ||||||
View content in all projects | ||||||
Edit content in all projects | ||||||
Create new projects | ||||||
Create a preview from a project | ||||||
Update all project connections | ||||||
Admin for all projects | ||||||
Invite users to organization | ||||||
Manage organization access and permissions | ||||||
Use dashboards as code (CLI) | ||||||
Rename models, dimensions, and metrics (CLI and UI) |
Full Access
, Can Edit
, Can View
Action | Full Access | Can Edit | Can View |
---|---|---|---|
View space content | |||
Manage space content | |||
Manage space access | |||
Manage space details |
Full Access
to a space can restrict and increase a user’s inherited project permissions in a space (e.g. you can make project editors into can view
in a space). Space permissions determine which users can edit space contents (charts and dashboards), view the contents in a space, and change a space’s settings:
Can view
access level to a space to see that the space exists and to see the charts and dashboards inside it.
Can edit
access level to a space to edit the content in the space (add/delete/rename charts and dashboards).
Full access
access level to a space to manage access to the space and to edit the space details (name, description, etc.).
Can edit
space permissions cannot get access to build or edit charts because Viewers don’t have access to the Explore view
Can edit
space permissions can save content in that space but not in any other space (unless given edit
access to another space)
Can view
space permissions cannot edit the content in that space, but they can create/edit content in other parts of the project (unless they’re given Can view
access).
Project Interactive Viewer
. She is a member of the Finance
group and the Design
group. The Finance
group is given Can View
access to the space. The Design
group is given Can Edit
access to the space. Priyanka has Can Edit
access to the space (inherited from the Design
group).
You can override a user’s group access by adjusting their specific user access.
E.g. Priyanka is a Project Interactive Viewer
. She is a member of the Design
group. The Design
group is given Can Edit
access to the space. I set Priyanka’s user access in the space to be Can View
. Priyanka has Can View
access to the space (her assigned user access to the space overrides her group access).
lightdash.com
). Generic email domains like gmail.com
or hotmail.com
are not accepted.
You can then select the access that you want these users to have by default. The organization Admin can always update a user’s permissions after they’ve joined!