Sharing Systems and Resources
Sharing gives a teammate a role on a System or Resource. Everyone works from the same Resource and its revision history, so there's one source of truth instead of copies passed around by email.
A Resource is more than a stored file. It's a file registered with the platform, either uploaded or connected from a third-party app, with its own ID, revision history, and permissions. When you share a Resource, you give access to that Resource and all its revisions, not a copy of the file.
Share a Resource
- Open the Resource and select Share.
- Search for a teammate by name or email.
- Choose a role: Can view (Viewer), Can edit (Editor), or Admin (Administrator).
- Select Share.
The roles you can give depend on your own role. For example, someone with Can edit access can share a Resource as Can view or Can edit, but not Admin.
Share a System
Sharing a System gives someone a role on every Resource the System tracks, so you don't have to share each file one by one.
- A Viewer on the System can view all of its tracked Resources.
- An Editor on the System can view and edit them.
- Removing someone from the System removes the access it gave them. Access shared directly on a Resource stays.
- Subsystems are shared separately.
To share a System, select Share System from its ⋯ menu, or add people under Settings > Members.
A role isn't the only check
A role decides what someone can do. Control tags and InfoSec levels, covered in the next lesson, can still keep a shared Resource closed to someone who doesn't meet them.
In the demo, one engineer opens the shared sensor specification because they have a role, the right control tag, and the right clearance. Another engineer can see the project, but without the tag and clearance, the file stays locked for them.