Get started with Delegate
Reach Beyond Delegate, sign in through your Beyond account, and find your workspace, your projects and the decisions that are waiting for you.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
Before you start
- You need a Beyond account. Delegate never asks for a password of its own.
- You need somewhere to work in Delegate: either the installation lets a new person start their own workspace, or a workspace administrator invited the address you sign in with.
- Delegate is not hosted.
http://delegate.localhost:5193is the local default address of a Delegate installation; there is no public one.
Sign in
- Open Delegate. The screen says "Welcome back." and "Sign in to review your projects and move work forward."
- If needed, change Language at the bottom of the screen. It works before you sign in.
- Choose Continue with Beyond Accounts. The note under it says "Your Beyond account signs you in here. You will be returned to this page."
- If you are not signed in at Accounts yet, sign in there. If you already are, nothing is asked.
Expected outcome: you are back in Delegate, signed in, on the project list titled "From repository to application."
When an installation signs people in through Beyond Accounts, that button is the only way in: the access key and direct provider buttons are not offered, and the server refuses them. An installation that is not connected to Accounts shows Continue with github or Continue with google, or only Sign in with an access key instead for the person who operates it. These pages describe the Accounts path.
If the return from Accounts fails, you are still on Delegate's return address and the browser shows a short technical response with a code, not a screen of the application:
| Code in the response | Meaning | What to do |
|---|---|---|
registration_closed |
You have no invitation and this installation does not let new people start a workspace. Inside the application the same refusal reads "This installation only accepts people invited to a workspace." | Ask a workspace administrator to invite the address you sign in with |
no_workspace |
Your account holds no seat. Inside the application: "Your account does not have a seat in any workspace." | Same |
platform_rejected |
The one-time hand-off from Accounts was refused: it was reused, expired or incomplete. Inside the application: "That sign-in could not be completed. Start again from the sign-in screen." | Open Delegate again and choose Continue with Beyond Accounts |
platform_unreachable |
Delegate could not reach Accounts to finish the hand-off | Platform unreachable. This is not a wrong password |
Once you are in, a refusal that arrives while the application loads is shown under the heading "Beyond Delegate is not responding." with its sentence and Try again. For example "Beyond Accounts is not answering. Nothing was changed; try again shortly." The sign-in form is not shown in that state, because signing in again would not help.
Your workspace and the free plan
The first time you sign in without an invitation, and if the installation allows it, Delegate creates your own workspace and makes you its Administrator. If you were invited, you land in the workspace that invited you, with the role they chose.
Open Workspace settings to see it. Under Plan you will find:
- Free: "One person works in this workspace. Inviting collaborators needs the paid plan."
- Paid: "This workspace can invite collaborators."
A seat is one person's place in a workspace. An invitation takes its seat from the moment it is sent. See Workspace and collaboration.
Find your way around
The sidebar has the active project first, then the workspace:
| Where | What it is |
|---|---|
| Project selector, with Choose a project when none is open | Switches project and keeps you in the same section |
| Projects | Every project you can read. New project appears for administrators |
| This project | Overview, Requests, Batches, Requirements, Planned releases, Versions, Infrastructure; and Manual import when you may configure the project |
| Needs my attention | Every question, evaluation, blocker and approval waiting for a person, across your projects. A number next to it counts them |
| Workspace settings | Name, plan, people and project access |
The button at the top left shows or hides the navigation (Show navigation, Hide navigation). Your initial at the top right opens your menu: Language, Appearance (Follow system, Light, Dark), Personal settings and Sign out.
If you see no project at all, either none is registered or nobody granted you access to one. Holding a seat is not access: see per-project access.
Register a project
Only workspace administrators can do this; others see "Only the workspace owner can register projects."
- Open Projects and choose New project.
- Fill in Project name, GitHub repository (HTTPS), for example the HTTPS address of the repository, and Test branch.
- Choose Register project.
Expected outcome: the project opens on Overview. Registering connects nothing: "Name the repository Delegate should work with. Choosing one from a connected account is not implemented." A repository that is already registered shows "This repository is already registered."
Start from what is waiting
Open Needs my attention. Its heading is "Decisions waiting for you." and each item names what it is, such as Intake question to answer, Proposed requirement to evaluate, Planned release scope to approve, Agent blocked · decision needed, Agent result to review or Test deployment to verify. Open takes you to the section where you resolve it. With nothing waiting it says "Nothing is waiting for you."
Next action
Write your first request, or invite the people you work with.
Related: Sessions and single sign-on · Delegate recovery · Supported limits