Expand the left-side menu and go to Project Settings > Users.

Then click on the + above the grid.

We recommend searching for your user's email in the grid to confirm they are not already in the system.

If they are, select the user and click Choose Items.

If not, click Create New in the bottom-left.

Remember to toggle the box for SSO on/off as needed. For these users, their Username and Email must be the same.

When you're done entering their info, click Save.

When adding them to the training project, make sure they have the permissions needed to access the self-paced training.

In most cases, you will give them the Trainee role + whatever they need pertaining to their job in O3. Reach out to your O3 trainer if there is any confusion.

Double-click on the user in the Project Users grid.

Then click into the Project Roles field and assign the necessary permissions.

This is also where you can make a user a Project Admin and assign them to a Project Team.

Select the user in the Project Users grid and click on the trashcan icon in the top-right.

This will only remove the user from the project. Reach out to a System Admin to have them removed from the site.

Expand the left-side menu and click on Project Settings > Associations.

Then choose the desired Entity Type at the top.

Click into a box to enable Associations to that Entity Type.

Associations are a one-way relationship. If you enable Associations for IWPs to Documents, it does not mean Document to IWP Associations are enabled. You will have to enable Document to IWP Associations separately.

The process for creating and editing these two fields is nearly identical. We use Disciplines for this example and clarify where there are differences.

In Project Settings click on Disciplines.

Then click on the + above the grid.

By default a Discipline Code is required.

You can tie Drawings to Disciplines so that whenever a work package of a specific Discipline is created, all its Drawings will be associated to the work package.

Click on Add Drawing and choose each Drawing as needed in the selection grid.

For Areas, click on Areas on the left and click on the +.

Areas can be associated to Units. When a Unit is chosen for a work package, only Areas tied to that Unit will show up in the Area picklist.

When adding upwards of 10+ Areas or Disciplines, it may be better to import them.

You can go to Tools > Data Requirements

and then search for your data type (like Areas) in the dropdown.

This will show you the column headers for that field. You can check each field you want included in the import and then click on the Create Import Template button in the top-right.

This will generate a CSV (the required file format for importing data into O3) with all the checked column headers.

After inputting your data go to Tools > Imports.

Then click on the + above the grid.

Choose your Import Type and provide the file.

You can flag imports as Update Only if you only want to update existing data and not create any new entries.

In Project Settings click on Lookups.

Lookups are configured for multiple Entities. For example, this is where you can add and remove Deliverable Types for your Deliverables.

Search for Deliverable Type in the dropdown at the top.

Enter the new Deliverable Type at the bottom and click Add.

Then click Save.

While this section will mostly apply to all Entity Types, we will use Installation Work Packages as an example.

Go to Project Settings > Entity Settings.

Then choose your desired Entity Type.

This is where you can set the "requiredness" for your Entity's data.

Configuring both Constraint Types and Approval Types is nearly identical. We focus on Constraint Types and clarify where there are differences.

Go to Constraint Types.

Then click on the + or select an entry in the grid.

See below for a description of each field.

Approval Types can be created under Approval Types.

You'll notice some similarities between the Approval Types and Constraint Types form.

Approval Types include Submitter Role and Approver Role. You can specify which types of users can do each of these actions.

Enabling the Hard Constraint field means the constraint will be included in the % Constraint Free calculation on a work package.

It can also be used to prevent a work package from transitioning to the next status.

Toggling off Hard Constraint means it will be a soft constraint. Soft constraints are not included in the % Constraint Free calculation and will not prevent the work package from transitioning to a new status.

An example of this would be a material delay. If a material is set to arrive on start a few days late, but you only need it towards the end of installation, then it doesn't make sense to stop installation altogether.

Toggle the Auto-Create flag in either the Constraint or Approval Type form.

Doing so will make the Auto Created Constraint Items section appear.

Click on Add Item.

Assign to Planner User lets you automatically assign the constraint or approval to whoever the specified Planner User is for an Entity.

You can also automatically assign the constraint or approval to a specific role (via Assigned to Role or to a specific individual (via Assigned to User).

With the Filters section, you can specify for which types of Entities this constraint or approval will be created for.

Click on the + > Add Filter Rule.

In the example below, this constraint will only be created for IWPs with a Discipline of piping.

Click on Execution Task Types at the top. Note this is only support for certain Entity Types.

And click on the + to create a new one.

Check out this article to learn more about configuring Execution Task Types.

In Entity Settings click on Statuses.

A status is really just a Name given to a State. A status's behavior is determined by its State.

For example, when I move an IWP into a status whose State is In Progress, the IWP's Actual Start Date is updated.

States have a set order.

Going out of order can have unintended consequences and mess up your dates that are populated upon status transition.

Color determines the color the status will have in the Gantt view and when visualizing your model by work package status.

Sort Order determines where it will show up in the dropdown.

Require Admin to Edit means that only a Project Admin can edit an Entity in this status.

We recommend this for Closed Out states, where no further work is needed on the work package.

You can restrict users from editing fields in this status with Locked Fields.

Pre-conditions are requirements that must be satisfied before you can enter that status. We cover all the different Pre-conditions here.

Here you can specify where the work package can go next.

In the example above my work package can go from Ready for Review back to In Development, or forward to Approved.

Filling in the Automatic box means that once that status's Pre-conditions are satisfied, the work package will automatically go to that status.

Constraints can be auto created in specific statuses. Note you need to create the Constraint Type first under Constraint Types. You can learn more here.

If you want a constraint to be auto created in this status, leave the Auto Create flag off.

Click Add Item to add a new Auto Created Constraint Item.

Then fill it out just as you would any other constraint.

Everything above applies to status-specific approvals, only you will need to go to Approvals in the status menu.

While we use Installation Work Packages in the below examples, the process is nearly identical for updating all forms.

Whenever you want to add a field to a creation form (e.g., for IWPs), this will not be done in Project Settings.

Instead, you will pretend like you are going to create a brand new IWP.

In the IWP's creation form, click on the Layouts icon in the top-right > Edit Layout.

You can add fields by clicking Add Field or remove fields by clicking on its x.

When you're done, click on the Layouts icon again > Save.

You can also update the layouts of your Detailed Forms as well.

We cover how you can do this here.

Check out some of our other Cheat Sheets!