Account Conventions/Roles for New Relic

What every new account in the organization you are working in follows: how it is named, the groups made for it, and the roles each group is given. Account Creation builds its form from this page. Only admins can open it.

Account name

A name is its parts joined by spaces. The parts start as Application|Team Name, Environment and Region, and each can be renamed. The first two are always required; any after them are required only if ticked. + Part adds another, up to eight.

Give a part a list of values, one a line, and Account Creation offers it as a dropdown and accepts nothing else. Leave a part without values and it is typed. A value is stored as it is spelled here, so prod and Prod do not make two different names.

Groups and their roles

Each group listed is made for every new account, named with the account's name followed by the group's: an account called Orders Prod with a group called Admins gets a group called Orders Prod Admins.

For each group choose the authentication domain it is made in, which is where its members sign in, and tick the roles it is given. The roles are read from New Relic as they are now, standard ones first and your organization's custom ones after, and only roles that can be granted on an account are offered. A group is given its roles on the new account alone. A group with no role mapped is refused, since it would give nobody access to anything.

Where accounts are made

The New Relic data center new accounts are made in, United States or Europe.

Saving

Save conventions writes the page as it stands. Nothing in New Relic changes when conventions are saved. Requests already waiting are checked against the conventions as they are when an admin reviews them, so a request whose name no longer fits is flagged then.