Use Delegate with a Beyond project
Link a Delegate workspace to a Beyond organization, arrive from Beyond Projects and attach a repository, adopt a project Delegate already has, and understand each refusal. These screens exist only in a Delegate installation that is connected to Beyond Projects.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
Before you start
Everything on this page appears in Delegate only when the installation is connected to Beyond Projects. Without that connection Delegate works as its own section describes, none of these panels exist, and nothing connects a Delegate workspace to a Beyond organization.
- You sign in to Delegate through Beyond Accounts.
- To link, attach or adopt you must be an Administrator of the Delegate workspace. For linking you must also be Owner or Administrator of the organization in Beyond Accounts.
Link the workspace to a Beyond organization
A Beyond project belongs to one organization, so Delegate has to know which organization the projects of a workspace belong to. That is an explicit decision by an administrator. Delegate never guesses it from a name.
- In Delegate, open Workspace settings and find the panel Beyond organization. Until it is linked it says "This workspace is not linked to an organization yet."
- Choose the Organization. The list holds only the organizations that Beyond Accounts reported you as owning or administering when you signed in.
- Choose Link organization.
Expected outcome: the panel shows Linked organization, its Organization identifier and when it was Linked.
| You see | Meaning | What to do |
|---|---|---|
| "Only a workspace administrator can link an organization." | Your Delegate role is not Administrator | Ask a workspace administrator |
| "Beyond Accounts did not report an organization that you own or administer when you signed in. Sign in again after your role changes there." | You are a Developer or Viewer in your organizations, or in none, or your role changed after you signed in | Get the role in Accounts, then sign out of Delegate and sign in again |
| "This workspace has projects attached under its current organization, so it cannot be linked to another one." | A workspace with attached projects cannot change its organization | Nothing. Unlinking and moving are not implemented |
Several workspaces may link to the same organization. Manage organizations in Beyond Projects opens Projects, when the installation configured its address.
Arrive from Projects and attach a repository
In Beyond Projects, open the project with Tasks and automation in Delegate. Delegate signs you in if needed and then shows what you may see for that project:
| What Delegate finds | What you see |
|---|---|
| One attached Delegate project that you can read | It opens directly |
| Several | They are listed under Attached in Delegate, each with its repository and branch |
| None, and you are an administrator of a workspace linked to the project's organization | The form Attach a repository |
| None, otherwise | "Nothing to open here", with the reason |
| Beyond Projects does not answer | "This Beyond project could not be opened." and Try again. Projects that are already attached still open during an outage; only a new attachment needs Projects |
To attach a repository:
- Read the introduction: "The project already exists in Beyond Projects, so it is not registered again. Delegate needs the repository and the branch its agents and deliveries work with."
- Project name and Project identifier are shown, not asked: "The name and the organization come from Beyond Projects and are managed there."
- Fill in GitHub repository (HTTPS) and Test branch. The branch starts as
main. - Choose Attach repository.
Expected outcome: the Delegate project opens on Overview. Repeating the same attachment after an uncertain answer completes it and creates nothing twice. One Beyond project can have several repositories in Delegate: on an attached project, Attach another repository is under Infrastructure, in the panel Beyond project identity.
The reasons under "Nothing to open here":
| The reason | What to do |
|---|---|
| "No Delegate project you can read is attached to this Beyond project. A workspace administrator can attach a repository to it." | Ask a workspace administrator to attach one, or to give you access to the attached project. Delegate does not say which of the two applies |
| "Your workspace is not linked to a Beyond organization yet. Link it in the workspace settings, then open this project again." | Link the workspace. An administrator also sees Open workspace settings |
| "This Beyond project belongs to a different organization than the one your workspace is linked to." | The project cannot be attached in this workspace |
| "This project is archived in Beyond Projects. Restore it there before attaching a repository." | Restore it in Projects. Refusing an archived project is Delegate's own rule: Projects itself would accept the link |
| "This project was deleted in Beyond Projects. Nothing can be attached to it." | Restore it in Projects while it is recoverable |
The link back to Projects
A Delegate project that is attached to a Beyond project shows, at the top of the project, Beyond project with the identity, as in "Beyond project prj_0f3c9a1b2d4e5f6071829304", and Open in Beyond Projects when the installation configured the Projects address. The link grants nothing in Projects either: you see the project there only as a member of its organization.
Adopt an existing Delegate project
Use this for a project that Delegate already has and Beyond Projects does not know.
- In Beyond Projects, an Owner or Administrator registers an existing project and copies its project identity.
- In Delegate, open the project, then Infrastructure, and find the panel Beyond project identity. It says: "This project is known only to Delegate. Attach it to the project that represents it in Beyond Projects. Its identifier, requests and history do not change."
- Paste the identity into Project identifier. The hint reads "Copy it from Beyond Projects. It starts with prj_".
- Choose Attach this project.
Expected outcome: the panel shows the Project identifier, Adopted with the date, and Name before adoption with the old name. The Delegate project takes the name it has in Beyond Projects. "The name and the organization are managed in Beyond Projects. Requests, planned releases and history stay in Delegate."
Anyone who is not a workspace administrator sees the form disabled and "Only a workspace administrator can attach this project." Nothing is ever matched by name: only the identity you paste decides.
The New project screen
With Beyond Projects connected, New project in Delegate starts with this notice: "This installation uses Beyond Projects. Create and manage a project there, then open Delegate from it to attach a repository. Registering here creates a project that Beyond Projects does not know." Open Beyond Projects follows it when the address is configured.
Registering in Delegate as before still works. Such a project has no Beyond identity until someone adopts it.
Refusals
Every refusal changes nothing.
| Message | Meaning |
|---|---|
| "This installation is not connected to Beyond Projects." | The connection is off. None of this page applies |
| "Beyond Projects is not answering. Nothing was changed; try again shortly." | An outage. It is not a refusal of your access. Try again later |
| "Beyond Projects refused this installation’s request. Nothing was changed; the operator has to check its credential." | A problem of the installation, not of your account. Tell the people who run it |
| "Another Beyond project already holds this Delegate project. Nothing was changed; an administrator of the organization has to resolve it in Beyond Projects." | One Delegate project belongs to one Beyond project |
| "This project is already attached to another Beyond project." | The same, seen from an adoption |
| "That Beyond project belongs to a different organization than the one this workspace is linked to." | Check the identity you pasted and the linked organization |
| "This workspace is not linked to a Beyond organization yet. Link it in the workspace settings first." | Link the workspace |
| "That project is archived in Beyond Projects. Restore it there first." | Restore it |
| "That project was deleted in Beyond Projects." | Restore it in Projects while it is recoverable |
| "This repository is already registered." | The workspace already has this repository as a project. Adopt that project instead of attaching the repository again |
Limits
Next action
Attached? Continue with Requests in Delegate.