Request Application Access
Overview
Use this guide to request access to P1 applications and environments.
P1 provides access to applications across IL2, IL4, and IL5 environments. Depending on the application and environment, you may need an authorized Onboarding Supervisor or Team Lead to submit the request.
Follow the steps below to determine which request to submit and what information is required.
WARNING
Requesting application access does not mean access is immediately available. An authorized person must submit requests, and they must be approved before access is provisioned.
Before you begin
Before submitting an application-access request, confirm the following:
- The user has a P1 account.
- The user has signed in to the P1 Portal at least once.
- You are authorized to submit the request.
- You know which application or applications the user needs.
- You know which environment the user needs access to.
- The requested access is appropriate for the user's role.
User must log in before access is requested
The user must log in to the P1 Portal at least once before an application-access request is submitted.
If the user has never logged in to the portal, their name may not appear in the user-selection fields on request forms.
If the user does not yet have a P1 account, see Create a P1 Account.
Who can submit an access request
Request submission permissions depend on the requested application.
| Request Type | Authorized Submitter |
|---|---|
| Standard application access | Authorized Onboarding Supervisor |
| Multi-application access | Authorized Onboarding Supervisor |
| Service Desk Agent access | Authorized Onboarding Supervisor |
| Argo CD access | Authorized Onboarding Supervisor or Team Lead |
| SonarQube access | Authorized Onboarding Supervisor or Team Lead |
| Iron Bank access | Authorized Onboarding Supervisor |
INFO
If you are not an authorized submitter, contact your organization's Onboarding Supervisor or Team Lead.
Choose the application access you need
Use the appropriate request based on the application or applications the user needs.
Multi-application access
Request application access when requesting access to one or more supported applications or environments in a single request.The application request may be used for:
| Environment | Applications |
|---|---|
| IL2 | Mattermost, Jira, Confluence, GitLab, IL2 Staging |
| IL4 | Mattermost, Jira, Confluence, GitLab, IL4 Staging |
| IL5 | Mattermost, Jira, Confluence, GitLab, IL5 Staging |
Select only the applications and environments the user requires.
SonarQube access
Request to add/remove SonarQube access when the user needs SonarQube access.Argo CD access
Request to add/remove Argo CD/App access when the user needs Argo CD access.Iron Bank access
Use the approved Iron Bank access request when the user needs Iron Bank access.
Jira Service Desk Agent access
Request Jira Service Desk Agent access when a user needs agent-level access to manage customer support tickets.Agent-level access may allow users to:
- View customer support requests.
- Manage service queues.
- Transition tickets.
- Respond to customers.
- Add internal comments.
- Perform applicable support workflows.
WARNING
Jira Service Desk Agent access requires a paid license.
When submitting the request, provide the organization's PBO or CTT number when required.
If the PBO or CTT number is unavailable, provide the applicable major command or organization, such as AMC, AETC, or ACC.
Select the appropriate environment
Make sure you request access to the environment the user actually needs.
| Environment | Applications |
|---|---|
| IL2 | Mattermost, Jira, Confluence, GitLab, IL2 Staging |
| IL4 | Mattermost, Jira, Confluence, GitLab, IL4 Staging |
| IL5 | Mattermost, Jira, Confluence, GitLab, IL5 Staging |
Not every user or organization is authorized for every application or environment.
If you are unsure which environment the user requires, contact your organization's appropriate POC before submitting the request.
Submit the request
After confirming the required application, environment, and authorization:
- Open the appropriate access request form.
- Select the user who needs access.
- Select the application or applications required.
- Select the appropriate environment, when applicable.
- Select the appropriate access or role.
- Provide any required organizational or authorization information.
- Review the request for accuracy.
- Submit the request.
TIP
Request only the access the user needs to perform their role. Requesting unnecessary applications or elevated permissions may delay approval.
After you submit the request
The request must be reviewed and approved before we provision access.
Once approved, application access may be provisioned automatically depending on the application and request type.
Automated processing may take approximately 10 minutes after approval. Processing times can vary by application and request type.
After the expected processing period:
- Have the user sign in to P1.
- Open the requested application.
- Confirm that the user can access the correct environment.
- Confirm that the expected application functionality is available.
If the user cannot access the application
If the user can successfully authenticate to P1 but cannot open the requested application, do not immediately reset the user's password or MFA.
First confirm:
- The correct P1 account is being used.
- The correct application was requested.
- The correct environment was requested.
- The access request was approved.
- The expected processing time has passed.
- The user is attempting to access the correct application URL.
If the issue continues, contact the Help Desk .
Provide the application name, environment, request or ticket number, exact error message, and a screenshot when available.
For authentication problems, see MFA & Authentication Troubleshooting.
Application access does not automatically include every service
Successfully authenticating to P1 does not automatically provide access to every P1 application.
Each application or environment may require separate authorization and provisioning.
For example, a user may be able to sign in to P1 but still need an approved request for Jira, Confluence, Mattermost, GitLab, SonarQube, Argo CD, or Iron Bank.
Need a different role or elevated permissions?
If the user already has application access but needs additional permissions or an elevated role, do not submit a standard application-access request unless the form specifically supports that change.
Instead, request to modify or remove a license .
WARNING
Some Jira Project and Confluence Space role changes require prior authorization from the appropriate Project or Space Administrator or Lead.
Common issue: User does not appear on the request form
If the user does not appear in the user-selection field:
- Confirm that the user has created a P1 account.
- Confirm that the user has logged in to the P1 Portal at least once.
- Confirm that you are searching for the correct user.
- Do not create another P1 account solely to make the user appear in the request form.
- Contact the Help Desk if the user still does not appear.
Common issue: Sorry, you have not been granted access to that application group
This message may indicate that the user does not have the required license or access assignment for the application.
Before submitting another access request:
- Confirm that the user is signing in with the correct P1e account.
- Confirm that the requested access was approved.
- Confirm that the appropriate processing time has passed.
- Verify the user's license or access assignment, when applicable.
- Contact the Help Desk if the issue continues.
- For Mattermost licensing, authorized Onboarding Supervisors should use the P1LM when applicable.
Contact the Help Desk
Contact the Help Desk if you are unable to submit an application-access request or if approved access is not available.When requesting assistance, provide:
- User's name.
- P1 username, if known.
- Email address associated with the P1 account.
- Application.
- Environment.
- Requested role or access level.
- Request or ticket number.
- Exact error message.
- Screenshot, when available.
Protect your account
Never include authentication secrets in an access request or Help Desk ticket.
Do not provide:
- Passwords.
- MFA/OTP codes.
- MFA QR codes.
- Recovery codes.
- YubiKey PINs.
- Other authentication secrets.