Projects: Control User Access
Understand your responsibilities for controlling access to projects.
On This Page
Access at a Glance
| Area | More information | 
|---|---|
| People who need access | 
 | 
| Authentication method: Authentication method that is used by the user interface or APIs | The way that you access a project determines your authentication method. You have the following options for accessing projects: 
 | 
| Authorization method: Role-based access control | Role-based access control governs access to a project and its integration components within an Oracle Integration instance, including actions that you perform using the Developer API for Oracle Integration 3. Role-based access control, sometimes called RBAC, determines the users and groups who can edit, view, and monitor a project. Role-based access control can be more restrictive than a
                  service role but can never give a user more permissions than a service role
                  allows. For example:
                                     
 Notes:
                                    
                                     
 | 
How to Control Access
| Security goal | Owner | More information | 
|---|---|---|
| Control the people who can access each project | 
 Instance users with the ServiceAdministrator role, or project administrators with the ServiceDeveloper role | Assign role-based access control within each project. To learn about role-based access control, and to set up access, see Control Who Can Edit, View, and Monitor in a Project in Using Integrations in Oracle Integration 3. | 
