@@ -412,6 +412,7 @@ If your team has special requirements for tours and you want to develop tours wi
- If a user actively utilizes the tool, we may **extend their access** or consider purchase additional licenses as needed.
- If a user is not actively using the tool, their license may be **reassigned** to another team member.
- To request access, open a request in Lumos (available in the Okta dashboard).
For questions or assistance, reach out to us in our team channel: [#dev-advocacy-team](https://app.slack.com/client/T02592416/CMELFQS4B).
#### Adding a new Navattic user (Developer Advocacy team process)
@@ -420,13 +421,14 @@ This section provides instructions for the Developer Advocacy team to onboard ne
When a team member requests access to Navattic, follow this process:
1.**Validate the request** – Ensure the team member provides a valid business justification for using Navattic.
2.**Check license availability** – Verify that our license pool allows adding more team members. Review the [Navattic users tracking spreadsheet](https://docs.google.com/spreadsheets/d/1x5T3rXhsqUZYHdMAz1BWt5gExNA_MLO9AtFpTVbzDwc/edit?gid=0#gid=0) to confirm available licenses.
3. Approve the request in Lumos.
4.**Send guidelines** – Share the [Navattic guidelines](#guideline-and-tips-for-creating-gitlab-tours-with-navattic) with the team member.
5.**Communicate the trial period** – Inform the team member that access is granted for a **default period of 3 months**, based on the [Requesting Access to Navattic](#requesting-access-to-navattic) process.
6.**Update tracking spreadsheet** – Add the team member to the [Navattic users tracking spreadsheet](https://docs.google.com/spreadsheets/d/1x5T3rXhsqUZYHdMAz1BWt5gExNA_MLO9AtFpTVbzDwc/edit?gid=0#gid=0) with their name, email, start date, and expected end date.
7.**Add to Slack channel** – Invite the team member to the [#navattic-updates](https://gitlab.slack.com/archives/navattic-updates) Slack channel for ongoing communication and updates.
1. The Navattic admin will receive the Lumos request via Slack or email.
2.**Validate the request** – Ensure the requester provides a valid business justification for using Navattic.
3.**Check license availability** – Review the [Navattic users tracking spreadsheet](https://docs.google.com/spreadsheets/d/1x5T3rXhsqUZYHdMAz1BWt5gExNA_MLO9AtFpTVbzDwc/edit?gid=0#gid=0) to confirm that our license pool has availability for an additional user.
4.**Approve the request in Lumos** – Once validated, approve the access request in Lumos for Okta access and Navattic account creation.
5.**Send guidelines** – Share the [Navattic guidelines](#guideline-and-tips-for-creating-gitlab-tours-with-navattic) with the team member.
6.**Communicate the trial period** – Inform the team member that access is granted for a **default period of 3 months**, based on the [Requesting Access to Navattic](#requesting-access-to-navattic) process.
7.**Update tracking spreadsheet** – Add the team member to the [Navattic users tracking spreadsheet](https://docs.google.com/spreadsheets/d/1x5T3rXhsqUZYHdMAz1BWt5gExNA_MLO9AtFpTVbzDwc/edit?gid=0#gid=0) with their name, email, start date, and expected end date.
8.**Add to Slack channel** – Invite the team member to the [#navattic-updates](https://gitlab.slack.com/archives/navattic-updates) Slack channel for ongoing communication and updates.
