Sign-up is self-service from the application: platform.betool.ai.
Step 1 — Sign up
- Open platform.betool.ai and click Create an account.
- Enter your email address (professional or personal), a password (minimum 8 characters, hashed with argon2id server-side) and, if you wish, your name and your organization's name.
- Signing up always creates a new organization, of which you become the administrator. If no name is entered, it takes the name of your domain (professional email) or your own name (public email: Gmail, Outlook…). Signing up never automatically makes you join a colleague's existing organization on the same domain: that requires an invitation.
You can also sign up and sign in with "Sign in with Google": the Google token is verified server-side, and you don't have a betool password to choose.
Step 2 — Your organization
Your organization is created at sign-up; a welcome screen then invites you to describe your company (optional step). The organization is the primary isolation boundary:
- All your data (pipelines, secrets, files, history) belongs to it.
- Your LLM keys are isolated: no other organization can access them.
- Roles and invitations are managed within this organization.
You can belong to multiple organizations with the same account (by accepting invitations). The organization menu, at the top of the admin panel, lets you switch between them (Switch organisation).
Step 3 — Invite your colleagues
From the organization menu → Organisation settings → Team, invite colleagues by email address (administrators only). A member's rights are set along two axes:
| Setting | Effect |
|---|---|
| Administration | Manages the organization's settings and members' access (invitations, sections, deactivation), as well as privacy settings |
| Allowed sections | Restricts a member's navigation to a subset of the admin (Usage, System, Knowledge & indexing, Tests, Support). Unlimited access by default |
Password recovery
From the login screen, "Forgot password?" sends a reset link by email (valid for 30 minutes by default). An organisation administrator can also trigger a reset for a member via the admin API (POST /api/admin/users/{user_id}/password-reset, audited action).