Vulcan: permissions
Who can create a Vulcan resource, what it depends on, and how access is managed once it exists.
What does it enable?
A Vulcan resource follows the same access model as every other DataOS resource: nothing is shared automatically, and every permission traces back to someone who granted it.
When you create a Vulcan resource, you become its owner and automatically receive:
Can Edit: update the Vulcan resourceCan Manage Access: grant or revoke access to it for others
A Tenant Admin holds that same authority over every Vulcan resource in the Tenant, whether or not they created it.
Who can create a Vulcan resource?
A user with the Tenant Admin, Data Admin, or Data Developer Tenant role can create a Vulcan resource, provided they also hold the permissions it depends on.
What do you need before you can create one?
A Vulcan resource runs on Compute, so it needs a Can Use grant on the Compute it references:
Compute
Can Use
The grant can come from either the Compute's owner or anyone who already holds Can Manage Access on it, including a Tenant Admin, who can grant the access to themself or others. That grant is audited either way.
What is the common access pattern?
DataOS access is deny by default: owning one resource never extends access to the resources it depends on.
That means:
the Vulcan resource owner manages access to it
the Compute owner manages access to the Compute
Anyone with Can Manage Access on a resource can grant access on it, even without being the original creator. Within the Tenant, a Tenant Admin can do the same across all of them.
If you need to use a Compute someone else owns, ask its owner (or anyone else holding Can Manage Access on it) for the grant first.
What happens after the Vulcan resource exists?
Once created, the owner controls who can work on it. A Tenant Admin can manage access to it too, even without having created it.
Typical grants on an existing Vulcan resource:
Can Edit
Update the Vulcan resource
Can Manage Access
Grant or revoke access for others
There is no Can Use permission on a Vulcan resource itself: access to what it depends on is governed by the permissions on each dependency.
For the full access model, see Access control.
Last updated
Was this helpful?