Getting access

gap

Ask the team lead which applications you will use and request only the access needed for your role. You do not need GitHub or source-code access to read this guide. The list below describes the accounts you may need. An owners table is missing, so this guide cannot yet name the responsible person for each system.

Ask the team lead for	Why you need it
Jira project LT at Latest Thinking Jira	Find and discuss assigned work
Relevant 1Password vault access	Receive approved shared account information
TestFlight invitation and current Android installation link	Install the staging app
Strapi staging admin account	Inspect and edit staging content
lt-core staging administrator account	Inspect workflow state and use authorized impersonation

Use Environments to distinguish staging from production. Access to one application does not grant a role in another. In particular, the Strapi Editor role is separate from lt-core roles.

The team lead can help arrange these accounts. Actual grants and the responsible people still need confirmation.

For maintainers: source references

These references require repository access. Everything needed to understand this page is explained above.

• implementation brief
• the TestFlight runbook
• infrastructure guidance