⌘K
ChangelogSign inJoin waitlist
Docs/Policy gates/Allowlist & trust
// POLICY GATES

Allowlist & trust

Two kinds of trust shape who can hand work to Leroy and how much vetting it gets. Inside your account, trusted teammates skip the intake gate so their tickets go straight to work. Around the whole product, access is an invite-only beta — you sign in with your Leroy account, and uninvited people are sent to a waitlist.

01 Trusted teammates

The intake gateexists to vet inbound signals — a Sentry alert, a Linear issue, a Slack request — before Leroy spends time on them. A teammate filing a ticket from the web app isn't an inbound signal; they're a trusted human who already decided the work is worth doing.

So tickets a teammate files from the web app skip the intake gate by default. They move straight into triage and planning without waiting in your Needs-you queue. The plan and ship gates still apply as normal — trust here only affects intake.

i
Scope. The intake bypass applies to intake only, and only to tickets created in the app. Work that arrives from a connected source (Sentry, Linear, Slack) always runs through whatever intake rule you've set for that source.

02 Trusted vs. gated

Every teammate on your account is trustedby default. If someone's submissions need a closer look — a new hire still ramping, a contractor, anyone whose tickets you want to eyeball first — flip them to gated on the team screen. Their app-filed tickets then run through intake review like everything else, pausing in your Needs-you queue until you approve.

Setting
What happens to their app-filed tickets
trusted
Skip the intake gate — straight into triage and planning. (Default.)
gated
Run through intake review — pause at intake review until you approve.
i
It's per person, and reversible. Toggle anyone between trusted and gated on the team screen at any time. The change applies to their future submissions.

03 Access (invite-only beta)

Leroy is in an invite-only beta. To bring a teammate onto your account, invite them from the team screen. An invite is what grants them access — once they accept, they sign in with their own Leroy account and show up on your team (trusted by default, as above).

People who aren't invited can't create an account on their own. New signups are gated to invites plus a waitlist: anyone who lands on Leroy without an invite is pointed to the waitlist rather than into the product.

04 Sign in vs. sign up

The two are different doors, and the beta gate only sits on one of them:

✓
Sign in
If you already have a Leroy account — your own, or one you were invited to — you sign in normally. If you have access to Leroy, you have access.
!
Sign up
New signups are gated. Without an invite, you're routed to the waitlist instead of getting an account.
i
The same account is your key everywhere. Your Leroy login is what authenticates the web app and the MCP server alike — if you can sign in to Leroy, your connected tools can sign in too.
← Prev
Policy gates