
Choose an access method
Plans and permissions
Roles assigned in a parent Organization also apply in its descendants.
User access
An endpoint user needs three things to reach an endpoint:- The endpoint uses a sign-in provider.
- The provider admits the user. Raily checks an endpoint grant for Raily-hosted sign-in. An external provider applies its own access rules.
- The AI client has the endpoint’s connect link. The user adds it in a personal setup, or a workspace owner or administrator adds it for members.
Two kinds of sign-in
Raily supports two sign-in models. Choose one before you add users to an endpoint because each model handles access differently.
Use Raily-hosted sign-in when you want to grant access by email and choose each user’s endpoints in Raily. The next section explains these grants.
Bring your own connects an identity provider you already run: Google, Microsoft Entra ID (Azure AD), Auth0, Okta, Keycloak, or any other OpenID Connect provider through the Custom option. You add one from Configure OAuth Provider on the Access page. Raily trusts your provider to decide who is allowed. Users admitted by your provider can reach the endpoint and appear in Raily after their first successful sign-in.

Add and manage users
Grant a user access through Raily-hosted sign-in.
Raily-hosted user grants
This section is about a Raily-hosted sign-in, where you control access from inside Raily. To open a Raily-hosted sign-in’s user list, go to the Sign-in providers tab, open the row menu at the end of the provider, and select Manage users. For a bring-your-own provider, select View synchronized users instead. Your identity provider manages that list.

Open sign-up
By default, an endpoint on a Raily-hosted sign-in admits only the people you add on the Users page. Turn on open sign-up when you want anyone with the endpoint’s connect link to create an account and start searching without an invitation. With open sign-up on:- Anyone who signs in with a verified email address gets access to that one endpoint on their first call. It does not give them access to any other endpoint, even one that uses the same sign-in.
- New users appear on the sign-in’s Users page as Self sign-up.
- Their searches count toward your usage. The endpoint’s rate limit applies to each user, but there is no limit on how many people can sign up.
Before you begin
- A paid plan. On other plans, the option is locked and says Open sign-up is available on paid plans.
- An existing endpoint that uses a Raily-hosted sign-in. You choose open sign-up when you edit the endpoint, not when you create it. For an endpoint on your own identity provider, your provider already decides who can connect, so the option does not appear.
Turn on open sign-up
1
Open the endpoint
Open the endpoint and scroll to the Security card. Who can connect appears under Sign-in provider.
2
Choose Anyone (sign-up required)
Select Anyone (sign-up required). Raily asks Open this endpoint to anyone who signs up? Select Open sign-up to confirm.
3
Save the endpoint
Select Save Changes. Open sign-up takes effect when you save.
Stop someone who signed up
On an open endpoint, block a person instead of removing them. Open their row menu, select Manage access, clear every endpoint, and select Save. They show as Blocked and cannot get back in, even while sign-up stays open. Remove user does not keep someone out of an open endpoint. It deletes their grant, and they join again on their next call.Turn off open sign-up
Edit the endpoint, select Invited users only under Who can connect, and select Save Changes. New people can no longer join on their own. People who already signed up keep their access until you block them.If you change the endpoint’s sign-in provider, the endpoint goes back to Invited users only. Turn open sign-up on again if you still want it on the new sign-in.
API keys for software
An app, a script, or a backend service authenticates with an API key instead of using a user sign-in. The endpoint keeps its sign-in provider for user access; the key is separate, for software. One key works against any endpoint you scope it to. Create keys in the endpoint form, or manage them on the API keys tab under Access.1
Create the key and choose its scope
On the API keys tab, select Create key. Enter a name, then choose one endpoint, several endpoints, or All endpoints in the selected Organization.
Select Create.

2
Copy the secret
Raily shows the generated secret once. Copy it into your secret manager before you close the dialog. Raily cannot show the same secret again.
Select Done after you have stored the secret.

3
Manage the key
Open the row menu to edit the key’s scope, rename it, rotate its secret, or revoke it.
Rotate the key if its secret may have been exposed. Rotation issues a new secret and keeps the key’s name and endpoint scope. Raily shows the replacement secret once. The old secret can still work for up to about 30 seconds because successful checks are cached briefly.Revocation is permanent, and a key must be revoked before you can delete it. A request can still succeed for up to about 30 seconds after revocation because of the same cache.

Removing an endpoint from a key’s scope can take up to about 30 seconds to apply, because a successful check is cached briefly. Widening a scope applies on the next call, since a refusal is not cached. A change to a Raily-hosted user’s endpoints applies on their next request. Neither needs you to reissue a link or a key.
Organizations
An Organization is a scope inside your Account. Organizations nest: a parent Organization can hold child Organizations beneath it. Every endpoint, sign-in provider, user grant, and API key belongs to one Organization.
Access flows down
A parent Organization’s sign-in provider can serve endpoints in its descendants. An All endpoints grant covers endpoints that use that sign-in in the parent and its descendants. A named grant covers only the endpoints you selected. Endpoints and API keys do not inherit. Each belongs to one Organization, and an API key can reach only endpoints in that same Organization, never a child or a sibling. Inheritance only works downward. A grant made in a child Organization does not reach the parent, and it never reaches a sibling. If a user signs in successfully but still cannot reach an endpoint, check which Organization holds their access first. When you view a child Organization, access that came from a parent shows in the list labeled with the Organization it came from. You change that access where it was granted, in the parent, not in the child.
Raily creates a hosted sign-in with each new Organization, so you may see one you did not add. If an older Organization does not have one, set up Raily-hosted sign-in.
Next steps
Add and manage users
Grant Raily-hosted access and send a connect link
Providers
Configure Raily-hosted or external OIDC sign-in
Connect to Claude
Add an endpoint to Claude and sign in
Analytics
Review endpoint usage