Users

Project Roles

In order for a user to have access to a Project, they must be added to the Project User list by inviting their email address and granting them a Project Role:

Role	General Description
Admin	Can manage project routines and assets
Standard	Can view, plan and analyse work across Aphex Field, Planner and Insight
Lite	Can only access Aphex Field to view and status assigned work

A user’s Project Role dictates what actions a user can take inside the Project, and what Aphex Apps they can access.

Project Permissions

Project Workflows	Project Admin	Standard	Lite
View Live Gantt	✔	✔	-
Add Task	✔	✔	-
Add Package	✔	✔	-
Add WBS	✔	-	-
Add User	✔	✔ (of type Standard or Lite)	✔ (of type Lite only)
Edit User Role	✔	-	-
Edit Own Role	✔ (Unless only one Project Admin remains)	-	-
Ready and Unready Plans	✔	✔	-
Review Plans	✔	✔	-
Publish Plan	✔	-	-
Promise Plan	✔	-	-
Update Published Versions	✔	-	-
View Published Versions	✔	✔	✔
Share Published Versions	✔	✔	✔
Run an Import	✔	-	-
Project Data	✔	✔	-
Edit Publications	✔	-	-
Project Assets
WBS	✔	-	-
Packages	✔	✔	-
Subcontractor	✔	-	-
Labour	✔	-	-
Plant	✔	-	-
Materials	✔	-	-
Users	✔	✔ (of type Standard or Lite)	-
Teams	✔	✔	-
Locations	✔	-	-
Calendars	✔	-	-
Delay Reasons	✔	-	-
Project Settings
Project Settings	✔	-	-
Publication Routine	✔	-	-
Lookahead Period	✔	-	-
Manage Integrations	✔	-	-
Archive Project	✔	-	-

Aphex App Access

A user's Project role also determines what Aphex Apps they can access.

	Lite	Standard	Admin
Aphex Field	✔	✔	✔
Aphex Planner	-	✔	✔
Aphex Insight	-	✔	✔

Project User States

Once a user has been added to a Project, they can be in any of these states:

User State	General Description
Pending/Invited User	Invited user that hasn’t created an account
Active User	Enrolled user who has access to the Project
Archived User	User who has been archived from the Project
Deactivated User	User who has been blocked from the Organisation

Archived, Deactivated and Removed Users

Archived and Deactivated users will be blocked from accessing the Project, and the Project will no longer appear in the User's Project list.

They will retain ownership of any tasks or packages, and all their data inside the project will stay intact. Once restored, they will gain immediate access back to the Project.

To permanently remove a User from a Project, they need to meet the following criteria:

They must first be Archived
They must not have Ownership of any Tasks or Packages

Once a User has been removed from the Project, all activity and contributions they made will be anonymised.

Project User Export

The total Project User list can be exported into a .csv file, with the following contents:

Name
Email
Status
Last Login
Role
Delegate
Reviewer

Teams

Users can be grouped into Teams to make it easier only to see work owned by the team members on the Gantt or Map.

All users who have been added to a Team will automatically have the Team pinned in their Space Selector for quick access.

The Team Leader will be the user who initially created the team. A Team Leader does not hold any extra permissions over other users.

Delegates

Allocating a delegate will allow one user permission to edit and update another user’s tasks.

A delegate can take all action on an owner’s work except for:

Deleting an owner’s task
Marking an owner’s clash as non-conflicting
Marking an owner’s plan Ready

Assignees

Assigning a user to a Task or Package will allow the user to edit and update work that they do not own.

If a user is assigned to a Package, they will also automatically be assigned to all new Tasks created inside the Package.

An assignee can take all action on work they’re assigned to expect for:

Marking a clash as non-conflicting
Deleting a Task
Duplicating a Task
Breaking down a Task
Editing an External ID

Assigning a user to work will also automatically populate their daily Tasklist in Aphex Field with their assigned Tasks.

Project Users and Teams