In Apinizer, it is not possible for a user to access a project they do not have permission for, or even perform an action that is not within their authority within the same project. Users need to have role/roles to perform operations in any project.When the system is first installed, commonly used roles (API Developer, API Analytics, API Manager, API Creator, Project Owner) come ready. Default roles can be used to authorize users or teams, or new roles can be defined.In Apinizer; there are 5 default roles: API Developer, API Analytics, API Manager, API Creator and Project Owner.
Default Roles and Permissions
API Developer
API Developer
Permissions:
- API Spec
- API Proxy
- Deploy/Undeploy
- API Proxy Group
- Global Policy
- Task Flows
API Tester
API Tester
Permissions:
- API Tester
API Analytics
API Analytics
Permissions:
- Analytics
API Manager
API Manager
Permissions:
- API Proxy
- Deploy/Undeploy
- API Spec
- API Proxy Group
- Global Policy
- Task Flows
API Creator
API Creator
Permissions:
- API Creation
API Security
API Security
Permissions:
- API Security
Project Owner
Project Owner
Permissions:
- API Creation
- API Spec
- API Proxy
- Deploy/Undeploy
- API Proxy Group
- Global Policy
- Analytics
- Project
- Project Members
- API Security
- Audit
- Import/Export
- API Portal Plans
- Activate/Deactivate API Products
- Publish on Portal
- API Products
- Task Flows
When a new project is opened, the user who creates the project automatically acquires the Project Owner role.
Creating a New Role
An image containing role creation settings is shown below:
| Field | Description |
|---|---|
| Name | Role name information for the created role. |
| Description | A description can be written to facilitate management related to the created role. |
| Authorities (Authorities) | Field where the permissions that the created role will have are selected. Role permissions are added by selecting the checkbox belonging to the relevant permission. |

