Roles
Introduction
Secoda provides the ability to declare fine-grained access controls through Custom Roles. Some examples of roles that can be created are:
Table Owners should be allowed to edit documentation, but not Tags.
Jenny, our Data Steward, should be allowed to edit Tags for any Dashboard, but no other metadata.
John, a Data Analyst, should be allowed to edit the Related Resources for a specific Data Pipeline he is a downstream consumer of.
The Data Platform team should be allowed to manage users and groups, view platform analytics, and manage roles.
Custom Roles are only enabled for Premium and Enterprise tiers.
What is a Custom Role?
Custom roles allow workspace administrators to create tailored permission sets that go beyond Secoda's default roles (Admin, Editor, Viewer, and Guest). With custom roles, you can define precise access levels for different teams and use cases within your organization.
Understanding Custom Roles
Custom roles provide granular control over:
Resource access (tables, dashboards, documents, etc.)
Feature permissions (API access, monitoring, automation, etc.)
Administrative capabilities
Unlike default roles which have predefined permission sets, custom roles let you:
Choose specific permissions for each feature
Set different access levels for different resource types
Create role-based access control (RBAC) that matches your organization's needs
Creating a Custom Role
To create a custom role:
Navigate to Settings > Members and permissions
Click on the "Roles" tab
Select "Create Role"
Provide:
Role name
Description
Select permissions for each feature category
Permission Categories
Custom roles can be configured with permissions across several categories:
User Management
Users: Create, update, read, or delete users
Groups: Manage group memberships and settings
Roles: Create and modify roles
Resource Management
Read: View resources and their metadata
Write: Edit resources and their properties
Manage: Full control including deletion. This includes management of properties including description, owner, tags, verified, etc.
Settings
Workspace: Configure general workspace settings
Security: Manage SAML and security settings
API Keys: Generate and manage API access
Properties: Configure custom properties
Billing: Access billing and subscription settings
Import/Export: Manage data imports and exports
Appearance: Customize workspace appearance
Features
AI Assistant: Configure and use Secoda AI
Quality Score: Manage data quality metrics
Questions: Create and manage Q&A
Automations: Set up automated workflows
Monitors: Configure data monitoring
Views: Create and manage custom views
Analytics: Access usage analytics
Queries: View and manage queries
Lineage: View and edit data lineage
Tags: Create and manage resource tags
Collections: Organize resources in collections
Best Practices
Principle of Least Privilege: Grant only the permissions necessary for each role
Document Role Purposes: Add clear descriptions to explain each role's intended use
Regular Review: Periodically audit custom roles to ensure they align with current needs
Permissions
Out of the box, Secoda is deployed with a set of default Roles. The set of default roles are Viewers, Editors, and Admins.
Manage is all permissions (Create, Update, Delete, and View)
User Management
Users
Manage
View
View
Groups
Manage
View
View
Roles
Manage
View
View
Resource Management
Resources
Manage
Create, Update
View
Settings
Workspace
Manage
View
View
Security
Manage
None
None
API keys
Manage
Create, Update
View
Properties
Manage
Create, Update
View
Billing
Manage
None
None
Import and export
Manage
None
None
Appearance
Manage
None
None
Features
Secoda AI
Manage
View
View
Quality score
Manage
Create, Update
View
Questions
Manage
Create, Update
Create, View
Automations
Manage
View
None
Monitors
Manage
Create, Update
View
Views
Manage
Create, Update
View
Analytics
Manage
View
None
Queries
Manage
Create, Update
View
Lineage
Manage
Create, Update
View
Tags
Manage
Create, Update
View
Collections
Manage
Create, Update
View
Last updated
Was this helpful?