Project Users and Teams
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:
Admin
Can manage project routines, assets & settings
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 Role Permissions
View Live Gantt
✓
✓
-
Board View
✓
✓
-
Add Task
✓
✓
-
Add Package
✓
✓
-
Add Folder
✓
✓ Depends on Project Settings
-
Add User
✓
✓ Only Standard or Lite
-
Edit User Role
✓
-
-
Edit Own Role
✓ Only if there is another Project Admin
-
-
Ready and Unready Plans
✓
✓
-
Review Plans
✓
✓
-
Publish Plan
✓
-
-
Promise Plan
✓
-
-
Update Published Versions
✓
-
-
View Published Versions
✓
✓
✓
Share Published Versions
✓
✓
✓
Run an XML Import
✓
-
-
Import via CSV
✓
✓
-
Project Data
✓
✓
-
Edit Publications
✓
-
-
Folders
✓
✓ Depends on Project Settings
-
Packages
✓
✓
-
Subcontractors
✓
-
-
Labour
✓
-
-
Plant
✓
-
-
Materials
✓
-
-
Teams
✓
✓
-
Locations
✓
-
-
Calendars
✓
-
-
Delay Reasons
✓
-
-
Blockers
✓
✓ Depends on Project Settings
-
Tags
✓
✓ Depends on Project Settings
-
Project Settings
✓
-
-
Publication Routine
✓
-
-
Lookahead Period
✓
-
-
Manage Integrations
✓
-
-
Archive Project
✓
-
-
Project Permissions
✓
-
-
App Access
A user's Project role also determines what Aphex Apps they can access.
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:
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 to see views owned or shared with the team members on the Gantt or Map.
Teams can be created and managed on the team's page within Aphex from the Model. The Team Leader will be the user who initially created the team. A Team Leader does not hold any extra permissions over other users.
Teams can be added to views. This view will appear in ‘Shared Views’ for each user within the team.
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:
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
Assigning a user to work will also automatically populate their daily Tasklist in Aphex Field with their assigned Tasks.
Last updated
Was this helpful?