Administrator roles

There are usually two administrator roles you can assign when you set an account as an administrator. One is owner and the other is administrator. 

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 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 administer owners

Multiple users can be set as either role.

Neither role can edit their own expiry date.

Accounts with an administrator role cannot be modified by bulk operations or be sent expiry warning emails.

Anything to watch out for?

Like personal accounts, accounts with administrator roles can access resources. This is an activity covered by our misuse monitoring, which means an administrator account can get banned by the system and would need to be re-enabled by another administrator user. If you are the only administrator account holder, you should consider using a different (non-admin) account for resource access.

Unlike personal accounts, a change to the email address needs to be approved by the account holder. This is managed by an email to the old address and if that is not available (e.g. a typo during setup) then you will need to delete and recreate the account.

See also:

• About administrator accounts

• How to make someone an administrator