What functions are available to the Site Administrator in the platform?

When you log in as the Site Admin, there is an additional set of administrator options available to you, accessible from the top navigation bar.

To access the Admin menu

In Hermosa theme: from the vertical ellipsis menu, choose Admin.

In Default Theme: click the wrench icon (Administration option).

Note: When you first accept an invitation to be a Site Admin, refresh the page to see the new icon. There might be a short delay before all available options are visible on the Administration left menu.

the following functions are available to the Site Admin on the Admin menu:

Config—Manage site look and feel, including managing default settings for APIs, apps, and groups, managing custom styles and resources, and setting up and managing login domains. See Configuration.

Settings—Configure settings for resources on the platform such as alerts, apps, APIs, connections, comments, discussions, groups, tickets, users, reviews, and business security. See Site Resource Settings.

Site—Configure basic site settings such as site URL, contact email address, and themes. See Basic Site Settings.

Site Admins—Manage site admins on the platform, including inviting and removing site admins. See Site Admins.

What is the relationship between a Site Administrator, Business Administrator, and API Owner?

When your platform is initially installed, configured, and deployed a Site Admin user is created at that time. Note that the default Site Admin also has the Business Admin role.

All other user accounts created via the platform are added to the Policy Manager instance where the tenant is defined.

Each user account is automatically assigned Registered Users Group and API Owner role.

The Site Admin configures the API Owner role based on the visibility requirements of the tenant and intended usage. For example, if the intended usage of the platform was to allow users to add an API, the API Owner role would be configured with an "Add" privilege. If the intended usage of the platform was to not allow users to add an API, no privileges would be configured.