Sharing and collaboration


Domino makes it easy to collaborate on projects and share project outputs.

There are two things that affect who has access to your project:

  • the project's visibility settings
  • the project's collaborators




Visibility settings

You can change your project's visibility by going to the Access & Sharing tab of the project's settings page.




There are three different visibility options:

  • Public
    • Anyone can view your files and runs, even if they don't have a Domino account.
    • If file exports are enabled, anyone can import your project files.
    • Only explicitly added collaborators can modify files, start runs, or import environment variables, unless you check the allow runs by anonymous users box described below)

  • Searchable
    • Anyone will be able to see that this project exists, and see its name and description in search results, but only explicitly added collaborators can see the project's contents.

  • Private
    • Only collaborators can view this project or discover its existence through search results.

If your project is publicly visible, there is an additional option to allow runs by anonymous users. This will allow users to start runs even if they don't have a Domino account. Runs started by anonymous users will show up as being started by the project owner.


Allowing anyone to run your code can be dangerous. Be careful granting this level of access, and make sure to think through any information you may be revealing, such as environment variables you have set in your project that contain bearer tokens, API keys, or passwords.




Managing collaborators

To grant other users access to a project, you can add them as collaborators. To add collaborators, you must be a Contributor to the project, or the project Owner.

Click Settings from the project menu, then click the Access & Sharing tab and scroll down to the Collaborators and permissions panel. You can add new collaborators by their username or email address. If you supply an email address belonging to a Domino user, that user will be invited to join the project as a collaborator. If you supply an email address that is not associated with an existing Domino user, an email will be sent to that address inviting them to join Domino.




The collaborators tab is also where you specify how each collaborator should be notified when runs complete. This can be a powerful tool to keep your collaborators in sync on the work that each person is doing.




Access levels

The owner of a project can set different access levels for collaborators from the Collaborators and permissions panel. The basic capabilities of the various types of project collaborators are as follows:

  • Contributors

    Can read and write project files, and start runs. On the Settings page, Contributors can read and write project environment variables, and they can invite new collaborators. Contributors cannot change hardware tiers, compute environments, or the access levels of collaborators.

  • Results Consumers

    Can only read files and access published apps.

  • Launcher Users

    Can only view and run Launchers, and see the launcher runs results. They cannot view project files.

  • Project Importers

    Can import the project, but otherwise cannot access it.

  • Owners

    Are the only users who can archive a project, change the owner, change collaborator types, set automatic workspace shutdown times, or change the project default hardware tier or environment.

For complete, itemized project permissions set on each type of collaborator, consult the tables below:


Files permissions

Permission Project Importer Launcher User Results Consumer Contributor Owner
Read files     x x x
Write files        x x
Add external Git repository       x x



Runs permissions

Permission Project Importer Launcher User Results Consumer Contributor Owner
Start Run       x x
Start Workspace       x x
Schedule Run       x x



Publishing permissions

Permission Project Importer Launcher User Results Consumer Contributor Owner
Run Launcher   x   x x
View App   x x x x
Publish App       x x
Unpublish App       x x
Invite users to App       x x
Change App hardware tier        x x
Publish Model API       x x
Create Launcher        x x


Settings permissions

Permission Project Importer Launcher User Results Consumer Contributor Owner
Set environment variable       x x
Invite collaborator       x x
Manage collaborator permissions         x
Change visibility setting         x
Change default environment         x
Change default hardware tier         x
Change project name         x
Handle merge request         x
Transfer project ownership         x
Archive project         x


Import permissions

Permission Project Importer Launcher User Results Consumer Contributor Owner
Import project   x x x
Was this article helpful?
3 out of 3 found this helpful