Model Permissions
Decide who can edit your semantic models — protect certified models from unintended changes while keeping collaboration easy.
Semantic models often represent weeks of work. Model Permissions give you control over who can change them, so your certified models stay reliable and your team can still collaborate safely.
How it works
Every model has an Owner — by default, the person who created it. The owner decides who else can edit the model by inviting Editors. Everyone else on the platform is a Visitor and can view the model but not change it.
| Role | Who | What they can do |
|---|---|---|
| Owner | Model creator | Edit, delete, and invite editors |
| Editor | Invited by the owner | Edit the model; cannot delete it or invite others |
| Visitor | Everyone else | Read-only access |
Inviting someone to edit
Open the model and invite a collaborator by email — they'll receive an invitation and become an Editor. Editors can make changes to the model, but they can't delete it or grant access to anyone else. Only the owner controls the collaborator list.
If Solid created the model for you
During onboarding, Solid sometimes builds starter models on your behalf. These models don't have a customer owner yet. Any modeler in your workspace can click Claim Ownership to take ownership and start managing access.
A note on coming features
Two things aren't supported yet — ownership transfer between users, and a self-serve "Request Access" flow. If an owner leaves your team and you need ownership reassigned, just reach out to Solid and we'll sort it out. Both features are coming soon.
MCP, Ask, and Data Chat users
Users who consume a model through MCP, Ask, or Data Chat are Visitors of the model definition. They can query the model and view its metadata, but they cannot edit the model, delete it, or invite collaborators. Only Owners and invited Editors can change the model itself.
This is separate from warehouse data access — row-level, column-level, and table-level permissions are still enforced by your data warehouse when SQL executes. See Controls and Safeguards for how that works.
Data-level security is separate
Model Permissions control who can edit the model definition itself. They don't affect what data users can query — row-level, column-level, and table-level access are enforced by your data warehouse based on each user's credentials. See Controls and Safeguards for how that works.
Updated about 1 month ago