Read access permissions

Owners and administrators can change the read access permissions for streams, repository workspaces, components, and files and folders. If a component or stream is owned by a team or project area, the process area permissions determine who can set read access permissions.

Project areas

When a project area is the owner of a component or stream, the read access can be set to one of the following:

  • The owning project area, so that the read access matches the read access of the project area.
    Note: Membership in the project area is not required.
  • An access group. To have read access, you must be a member of the access group (either explicitly added individually to the access group, or a member of the project area or team area that is contained in that access group).

Team areas

When a team area is the owner of a component or stream, the read access can be set to one of the following:

  • The parent project area of the team area, so that the read access matches the read access of the parent project area.
    Note: Membership in the project area is not required.
  • The owning team area, so that you must have read access to and be a member of that team area to have read access.
  • An access group. To have read access, you must be a member of the access group (either explicitly added individually to the access group, or a member of the project area or team area that is contained in that access group).

Contributors

When a contributor is the owner of a component or repository workspace, the read access can be set to one of the following:

  • Public to everyone.
  • Private to the owning contributor.
  • Scoped by project area, so that the read access matches the read access of the project area.
    Note: Membership in the project area is not required.
  • An access group. To have read access, you must be a member of the access group (either explicitly added individually to the access group, or a member of the project area or team area that is contained in that access group).

Files and folders

The read access of files and folders can be set to the following states:

Note: When you check in a new file or folder, it inherits the read access from its parent folder.
  • The containing component. This is the default visibility on files and folders - read access is determined by the containing read access state of the component.
  • Private to a contributor.
  • Scoped by project area, so that the read access matches the read access of the project area.
    Note: Membership in the project area is not required.
  • Scoped to a team area, so that you must be a member of that team area to have read access.
  • An access group. To have read access, you must be a member of the access group (either explicitly added individually to the access group, or a member of the project area or team area that is contained in that access group).

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki