What Else Can I Do Within a Project?

Depending on your project membership status, your permissions allow you varying privileges.

Note: In any project, an organization administrator can assign himself or herself the Project Owner role. This will grant them the same project permissions as any other project owner. An organization administrator can’t even open a project unless they are a member and, even then, it is the project membership type that determines their project permissions.

Visit the topics listed under On This Page, to the right, to see what privileges come with each project membership.

Permissions for Working with Git Repositories

Here’s how you can interact with Git repositories, depending on your project membership status:

Action	Project Owner	Developer	Developer Limited	Contributor	Non-member
Create a hosted Git repository, add an external Git repository, or import a Git repository
Clone the Git repository
Push commits to the Git repository
Set a Git repository's default branch
Set Git repository branch restrictions
View file contents and commits
Create or delete branches and tags
Compare files and revisions
Lock or protect a branch
Download an archived branch or a tag
Add comments to commits
View graphical history of commits
Index a Git repository
Delete a Git repository

Both Developers and Developer Limiteds can use the VB Studio UI to create repositories, but must use the Git command line to delete the repositories created with the UI. Project Owners can delete repositories by using the Project Administration pages.

Non-members can clone a Git repository and make commits to it, but they can’t push the commits to the remote Git repository.

Permissions for Merge Requests

Here’s what you can do with merge requests, depending on your project membership status:

Action	Project Owner	Developer	Developer Limited	Contributor	Non-member
Create a merge request
Add comments or reply to a comment
Subscribe to merge request email notifications

Reviewers are automatically subscribed to merge request email notifications. Non-members can subscribe to email notifications by opening the merge request and clicking the CC Me button.

When a merge request is created, all reviewers are assigned the Reviewer role. The individual that submits the request is assigned the Requester role. This table lists additional actions Reviewers and Requesters can perform:

Action	Requester	Reviewer	Other Users
Add or remove reviewers
Approve or reject a merge request
Merge branches or close a merge request

A Project Owner can approve or reject a merge request, merge branches, or close a merge request, even if he or she isn’t assigned the Reviewer role.

Permissions for Maven

Here’s how you can interact wioth a project’s Maven repository, depending on your project membership status:

Action	Project Owner	Developer	Developer Limited	Contributor	Non-member
Browse the Maven repository
Download artifacts from the Maven repository
Upload artifacts to the Maven repository
Search artifacts in the Maven repository
Configure the automatic cleanup of the Maven repository

Permissions for Docker

Here’s how you can interact with Docker registries, repositories, and images, depending on your project membership status:

Action	Project Owner	Developer	Developer Limited	Contributor	Non-member
Link an external Docker registry
View external Docker registries, their repositories, and images
Download an external Docker registry repository's image manifest
Delete an external Docker registry repository's image manifest

Permissions for Jobs, Builds, and Pipelines

Here’s how you can interact with a project’s jobs, builds, and pipelines, depending on your project membership status:

Action	Project Owner	Developer	Developer Limited	Contributor	Non-member
Set up connections to OCI Compute and OCI Object Storage
Create, configure, and manage build executor templates
Add and manage VM build executors
Create a job
View job details
View job configurations
Edit job configurations
Run a build
Download artifacts
View logs, including build console, audit, and Git polling logs
Disable or delete a job
Create a pipeline
Configure a pipeline
View a pipeline’s instances
Delete a pipeline

Permissions for Releases

Here’s how you can interact with releases, depending on your project membership status:

Action	Project Owner	Developer	Developer Limited	Contributor	Non-member
Create a release
Clone or edit a release
Delete a release

Permissions for Environments

Here’s how you can interact with a project’s environments, depending on your project membership status:

Action	Project Owner	Developer	Developer Limited	Contributor	Non-member
View an environment
Create/delete an environment
Add an instance to/remove an instance from an environment

Project owners are the only project team members who can delete environments that were created in a different identity stripe. If a project member with the Developer role attempts this operation, they’ll see an error message informing them that they can’t delete an environment that has resources from another identity stripe.

An IDCS resource cannot be removed from an environment if the instance is in another identity stripe. Nobody can remove an IDCS resource from a different identity stripe from an environment, but the project owner can still delete the entire environment. In addition, an IDCS resource from a second identity stripe cannot be added into the same environment.

Permissions for Workspaces

Here’s how you can interact with a project’s workspaces, depending on your project membership status:

Action	Project Owner	Developer	Developer Limited	Contributor	Non-member
View a workspace
Create and manage a workspace

Managing a workspace includes such tasks as renaming, assigning a new owner to, and deleting a workspace.

Permissions for Issues

Here’s how you can interact with a project’s issue tracking system, depending on your project membership status:

Action	Project Owner	Developer	Developer Limited	Contributor	Non-member
Create an issue
Update an issue
Create and configure issue products
Create and configure issue tags
Create and configure issue custom fields

Permissions for Agile Boards and Sprints

Project memberships Here’s how you can interact with a project’s Agile boards and sprints, depending on your project membership status:

Action	Project Owner	Developer	Developer Limited	Contributor	Non-member
Create a board
Use Scrum board
Use Kanban board
View burndown charts and sprint reports

When you create a board, you become the owner of the board. As the board owner, you have special privileges over the board and sprint-related actions:

Action	Board Owner	Other Project Members	Non-Member
Add issues to a sprint
Start a sprint
Delete a sprint
Configure the board

Permissions for Wikis

Here’s how you can interact with wiki pages, depending on your project membership status:

Action	Project Owner	Developer	Developer Limited	Contributor	Non-member
Set the organization's default wiki markup language
Set the project's wiki markup language
Create a wiki
View a wiki page
Edit a wiki page		By default	By default
Delete a wiki page		By default	By default

The Project Owner (or member, if allowed) can grant edit and delete rights over a wiki page to all users, or restrict edit access to members or Project Owners only.

Permissions for Snippets

Here’s how you can interact with snippets, depending on your project membership:

Action	Project Owner	Developer	Developer Limited	Contributor	Non-member
Create a snippet
View snippet files
Insert a snippet file or copy a snippet file’s text
Clone the snippet Git repository
Push the commits to the snippet's Git repository
Download the archive of the snippet's Git repository
Like a snippet
Add comments

A non-member can clone the snippet’s repository and make commits, but can’t push the commits to the snippet’s Git repository.

If you’re a snippet owner, you can also perform these actions:

Action	Snippet Owner	Other Project Members	Non-Member
Add, update, or remove snippet files
Create a snippet from the selection
Delete a snippet