Developers & reviewers
Ask the product, explore behaviour, inspect impact and review business-logic changes without switching to a different source of truth.
A person signs in and works in a browser: ask the product a question, compare a document with it, ask what a part you are about to change reaches, write down work, and see what changed since last time. There are three roles. An owner also handles repositories, people and billing. A member asks, pulls and rebuilds. A viewer can only ask, and does not take a seat.
Invite a colleague by email from the People screen
Give them owner, member or viewer
They sign in and get the models your team has already built
A viewer reads and asks; a member can also pull and rebuild
Change a role or remove someone later from the same screen
A role applies to the whole team, not per project or per repository — you cannot hand someone one client project and hide another. A member can spend the team's shared credits, because rebuilding a model costs credits. A viewer's key is refused by the three things that write — confirming what a phrase means, taking a task and closing one — and the Access page says so on their screen so the refusal is not a surprise. The last owner cannot change their own role.
See it on a real product.
Three models are published in full and open without an account. Ask one of them the question this page is about.