Different entities in Domino can be permissioned separately. Permissions affect who is allowed to find and use specific entities. To summarize:
| Permission options | Details and subtleties | |
|---|---|---|
Projects | The Project visibility level can make Projects accessible to everyone if desired. Otherwise, Projects can have specific users and groups as collaborators. Collaborators can have specific roles that limit what they can do within the Project. | For Git repos attached to a Project, you’ll have to manage access through your Git host. The Discoverable visibility setting can make Projects appear in search results for users who don’t have access to the Project’s contents. |
Datasets, Data Sources, and External Data Volumes | These entities can be shared with specific users or groups. | To use any one of these features within a Project, a user needs access to the Project and to the respective data entity. |
Apps | Apps are permissioned independently of their parent Project. See Apps for more details. | You can permission an App to be accessible by anyone, even users without a Domino user identity. You can also allow users to request access to an App. |
Compute Environments |
Some configuration records settings, only accessible by admins, affect aspects of how collaboration on Domino works. For the full list of options, see Configuration records.
| Config key | Description | Example value |
|---|---|---|
| If |
|
| Whether users can mark Projects as public. |
|
| The default “visibility” level for new Projects. |
|
| Comma-separated list of file extensions to index for search. | txt, out, tsv, rtf, err, log, tex, latex, README, ipynb, py |
| Comma-separated list of Domino entities to index for search. | project, file, data_set, comment, model, run, environment |
| Whether search is enabled. |
|
| Maximum size of a file (kilobytes) to index for search. | 2048 |