Create - Administrator account

Path to function: Accounts > Create > Administrator account

This process is almost identical to adding a personal account - the differences are:

You select an administrator role at the start
Administrator accounts do not use any of the settings from the account preferences page
The new account will have an opportunity to change their password even if you set it

Roles

All will have at least one of these two roles available:

Owner

Can access all available functions including the schema editor, release policies and domain-wide settings
Can administer all users and all sub-organisations
Can switch into all sub-organisations (e.g. to manage permission sets)
Can create and administer other owners and administrators
The account must sit directly under the domain organisation

Administrator

Can access all functions except the schema editor, release policies and domain-wide settings
Can administer and switch into their own sub-organisations
Can be under any organisation or sub-organisation
Cannot create or administer owners

Depending on other settings you may also see:

Service provider administrator

Allows publishers and similar to access and administer the resources they enable in the OpenAthens federation

Service provider report viewer

Allows a reports only view of the SP dashboard for publishers and similar

Login details (continued)

Username - must exist, even if they’ll be using their email address in the next step. 6 - 20 characters long, including the prefix, English characters only, sorry.

Login by email address - can they use their email address instead of their username when signing in? If they have a separate user account for accessing resources, that may make a difference to this choice

Expires on - you can set it up to 5 years in the future.

Create account and - The first and third options will both send the same activation email - so if you do set a password the user will have an option to set a different one. The middle option will save the account in an unactivated state.

Details

The mandatory fields from your account schema

Optional details

The non-mandatory fields from your account schema

Permission sets

Whilst we usually recommend keeping them separate, you can access resources using an admin account. If you use restrictive mode then selection of permission sets will be important.

Once finished, hit the create account button and you’re done. Your colleague will get an email confirming things in a moment or two.

Anything to watch out for?

Just like personal accounts, misuse monitoring is in place and admin accounts can find themselves banned