Administrator Setup

In This Article

• The Two Administrator Roles
• Step 1: Add an Administrator
• Step 2: Assign Administrators to Registered Models
• Who Gets Notified
• Admins on a Guardian Link Model

Guardian provides two types of Administrators: Company Administrators and Project Administrators. The dual administrator levels allow for the proactive management of the project models to be delegated directly to people assigned to the project.

The Two Administrator Roles

Two roles provide delegated day-to-day model control to the people on each model while keeping firmwide standards with a smaller group.

Step 1: Add an Administrator

Every administrator, of either role, must first be added on the Administrators tab of Company Settings. This tab lists all administrator licenses on your Guardian account.

Note: The company’s first Company Administrator is assigned by the Guardian team when the account is created.

1. Open Company Settings and select the Administrators tab
2. Click Add New‍
3. In the Add/Edit Administrator dialog, fill in the fields below
4. Click OK

Choosing Auto Add and Allow Add

Company Administrators can always add themselves to any project, whatever these options say.

Step 2: Assign Administrators to Registered Models

Assign administrators to registered models in the Registered Projects dialog.

1. Open Registered Projects (Settings > Registered Projects)‍
2. In the Administrator column, click the cell for the model. It shows the admin's name, <Multiple>, or <None>‍
3. In the Administrator dialog that opens, click Add New and choose from the available Company and Project Administrators
4. To remove an admin, select their name and then click the delete button

Tip: Hold Ctrl and click to select several models, then edit their administrators at once.

Who Gets Notified

A Company Administrator who isn't assigned to a model won't get its instant alerts, unless the model has no admin at all.

Recommended: Turn Off Auto Add if You Have Few Admins

If your firm uses only a few admin licenses, uncheck Auto Add for each admin on the Administrators tab. Models then stay unassigned until you assign someone, and Guardian sends unassigned model alerts to every admin. That keeps everyone informed about every registered model.

Admins on a Guardian Link Model

In beta

Guardian Link lets one company, the Primary Project Team, keep its Guardian standards and protections in force on a model while other companies, Linked Collaborators, work in it. Guardian Link doesn’t add new roles or permissions. It changes where each company’s administrators can act.

What Linked Collaborator Administrators Can Do

On the Primary’s model, a Linked Collaborator’s Company Administrators and Project Administrators are treated like regular users for anything the Primary owns:

• They can view the Primary’s configurations and the model’s administrator list, but can’t change them.
• They aren’t added to the Primary’s administrator list, and Make Me Admin is greyed out for them.
• Project Administrators: while a Linked model is active, Project Configurations, Registered Projects, User Overrides and One-time Password aren't available to them, and the Link icon shows them the same read-only view an end user sees. They can still accept a Link from the dialog that appears when they open the model, or from Registered Projects with one of their own models active.
• Company Administrators: on a Linked model, Model Settings and Model Cleanup are greyed out, and the model's administrator list is read-only.
• Company Settings is unchanged. It stays company-wide and shows the same content whether a Linked model is open or not.

Override Passwords and One-Time Passwords on a Linked Model

A Prevent prompt accepts two kinds of password, and on a Linked model they don’t always come from the same company:

• The override password (the reusable one) follows the protection’s settings. Project protections and Sync Traffic Control on a Linked model use the Primary’s settings, so they use the Primary’s override password. Company-level command protections use your own company’s settings and password.
• A One-Time Password always follows the company on your Guardian license, whichever model you’re in.

So a Linked Collaborator user stopped by one of the Primary’s project protections can get past it with either the Primary’s override password or an OTP from their own company. An OTP generated by a Primary administrator won’t work for them.

This will change at general availability.

The split above is how One-Time Passwords work during the Guardian Link beta. At general availability, only the Primary’s passwords will work on the Primary’s models, for every user in the Link.