English

العربية

English

العربية

Appearance

Roles and Types of Users ​

Your organization assigns one or more roles to your account. Roles control which menus and actions you see. This page explains the main categories in plain language; for the exact menu-by-menu breakdown, see Reference — roles and visibility.

Consuming users and producing users ​

Consuming users use APIs that others have published. They browse the catalog, create My Applications, obtain credentials, and call services. They often work in consumer teams that share applications and collaborate on using APIs.

Producing users are responsible for publishing and maintaining APIs in the portal. They are commonly members of a backend team. Backend teams can own or manage APIs in the catalog and coordinate changes with consumers.

The same person can be both a consumer and a producer if your organization sets up their access that way.

Typical signed-in user (non-administrator) ​

A regular developer without the administrator role does not see the Admin section or organisation Settings, and does not manage permission groups on behalf of the whole organisation. Otherwise they can use the full consumer/producer workflow above.

Administrator ​

Administrators can do everything a typical user can, plus configure environments, permission groups, and organisation-wide settings. They are still subject to environment and product configuration (for example which gateways exist).

CI/CD role ​

Some accounts have a role used for automation and continuous delivery of API specifications, typically paired with the API-dex CLI — a separate tool from the web application described in this portal. Refer to your internal CLI documentation for commands and authentication.

Subscription manager role ​

When your organisation enables the related product, people with the subscription manager role may see Companies in the sidebar. They focus on company-level access to applications and subscriptions in that area. This guide does not describe every Companies screen or business rule — follow the in-app labels or ask your subscription owner.