For the complete documentation index, see llms.txt. This page is also available as Markdown.

Access & Governance overview

Set up who can enter your app, what each person can do, and how you verify access before sharing it.

Start with one complete access flow

  1. Choose a built-in role for an intended user.

  2. Invite that user by email and confirm their team.

  3. Configure authentication for the audience.

  4. Use the audit trail and system logs to investigate unexpected behavior.

Find the right guide

Section
What you will accomplish

Invite people, manage membership, and import or export user records.

Choose built-in roles and organize people into teams.

Choose and troubleshoot a sign-in method.

Define access to pages, actions, and records.

Review AI-generated changes and verify each user experience.

Find activity and diagnose errors.

Understand storage, credentials, and recovery responsibilities.

Four concepts to keep separate

Authentication establishes identity. Membership and teams associate people with the app. Authorization determines permitted actions and records. Publishing makes an app version available to its audience.

A successful sign-in does not prove that a user has the right permissions. A successful preview does not prove that a record-level restriction is enforced.

The written guides use the current Users and More navigation. Older provider tutorials and Classic builder examples are labeled where their screens differ.

Was this helpful?