Overview
You share a Project by adding collaborators to it. Each collaborator gets a role that determines what they can do, from read-only access to results up to full contributor rights. Comments on files, Jobs, and the activity feed keep the discussion attached to the work itself.How it works
Two settings control who can do what in a Project:- Visibility determines who can find the Project.
- Collaborator roles determine what each invited user can do. Project roles are independent of a user’s role in Domino.
Best practice: Audit your collaborators regularly and keep permissions as locked down as possible. Verify that each user has the permissions their work needs and no more, and use the visibility setting to limit who can see the Project.
Invite collaborators
You must be a contributor or the Project owner to add collaborators.- In the Project, go to Settings > Access & Sharing.
- In the Collaborators and permissions section, enter a username, email address, or organization name, then click Invite. An email address that doesn’t belong to a Domino user sends an invitation to join Domino.
- Set the collaborator’s Role:
- Contributor: read and write Project files, start runs, read and write environment variables, invite collaborators, and change the default Hardware Tier and Environment.
- Results Consumer: read files and access published Apps only.
- Launcher User: view and run Launchers and see their results only; no access to Project files.
- Project Importer: import the Project, but no other access.
- Owner: the Project’s owner (not assignable here). Only owners can archive the Project, change the owner, change collaborator types, share environment variables and files between Projects through import and export, or set automatic Workspace shutdown times.
- In Notifications preference, choose how to notify the collaborator when runs complete.
Collaborator permissions
These tables list the exact permissions for each role.File permissions
Run permissions
1 Start a Workspace: A user can start a workspace they’ve created.
Publishing permissions
Settings permissions
Dataset permissions
See Dataset roles for more information.Import permissions
Experiment permissions
Add comments
Use comments to document decision rationale, analysis, suggestions, and next steps where the work happens:- Files
- Jobs
- Job comparisons
- Activity feed
- Reviews
In the Project, go to Files, open the file, enter your comment in the Discussion box at the bottom, and click the send icon.
@ followed by their username in the comment. You can notify the Project’s collaborators. An organization added as a collaborator grants that access to every member, so you can notify any of them. In a Public Project, you can notify any user.
View Project activity
The Activity feed (under Overview in the Project menu) records the Project’s history: Jobs and Workspaces started, and comments on Jobs, Workspaces, and files. Filter the feed by type, and download it as a PDF. Select two completed runs in the feed to compare them. A read-only Status badge next to the Project name shows the Project’s current status.View event notifications
Administrators send notifications about Domino events such as planned maintenance or reminders to save your work. The Notifications panel is at the bottom right of the Domino home page and refreshes every 30 seconds. Click View All to see the past 30 days, filter by priority, and click Mark all as read to acknowledge them; messages sort chronologically with critical unread first, then default unread, then read and expired. Expired messages are tagged EXPIRED and disabled, and deleted messages disappear from your list.Related
- Project settings: visibility and environment variables.
- Manage Projects: forks, merges, ownership transfer, and sharing content between Projects.