For users to perform activities in P6 for iOS or P6 for Android, you will need to:
- Ensure the users you want to use the P6 mobile apps have a valid account in P6.
Note: Each user with a valid user account can be assigned to activities as a resource assignment if the account is associated with a labor resource, as an activity owner, or by being assigned a Team Member work distribution filter.
- Assign users to at least one module access option.
- Assign users to one or more activity assignments for at least one active project. P6 mobile apps will show activities that have not yet started, active activities, and activities completed in the last 30 days.
Note: OBS access to a project is not required for resource assignments or activity owners using P6 Team Member Web, Email Statusing Service, or P6 mobile to view and update their assigned activities. OBS access is required for each user with a Team Member work distribution filter assigned.
Have your P6 mobile app users download and install P6 for iOS from the Apple App Store or P6 for Android from the Google Play Store to their mobile device.
Note: The users will need to know the P6 server and their SSO username and password (if using SSO) or their P6 username and password (if using native authentication).
Upgrading Notes - P6 for iOS only
If your company is running an older version of P6 EPPM, users can install and use the latest version of P6 for iOS; however, they may not be able to use all the features of P6 for iOS.
Error Message
If users receive one of the following messages, an SSL certificate may need to be obtained from a trusted certificate authority.
- iOS: "Server URL points to an invalid web application."
- Android: "Cannot connect to server."
Known Issues
- If users are in a time zone that observes daylight savings time, the hours displayed in their activities may be incorrect by one hour.
- If users do not have any activities assigned to them, they might receive the message "Some data failed to load. Refresh to try again." on the Home page of the app. This issue will only occur if your company has version 8.2 deployed on the P6 application server.