Help and resources

Find the guide that fits.

  • The in-app help center is role-aware, with articles for every app.
  • Deep links open the exact screen your account can reach.
  • Public pages route product, adoption, and security questions.

How it works

Concrete product states, permissions, and handoffs

Each demonstration uses fictional sample data and keeps the source record, actor, permission boundary, and next step visible.

For product questions

Use the blog and product pages to understand workflows, AI boundaries, permissions, and integrations before you sign in.

For existing users

The in-app help center is role-aware and includes deep links into screens that your account can open.

For adoption work

Implementation and customer success pages explain migration, validation, training, governance, and ongoing configuration health.

Questions

What buyers usually ask

Answers are scoped to repository-verified behavior or intentionally point to current customer documentation when policy facts are not public.

No. The marketing examples are compressed, but the product path still checks the acting user, role, group scope, and domain permission before data is shown or changed.

Next step

Build a people operation your team will actually use.

Start with the workflow you want to make calmer, then map the people, records, permissions, and handoffs that make it real.