Open a project in Workspace, Delegate or CDN
A project has one entry for each product. Each entry takes you there with the project in context, and the product checks your access when you arrive.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
Before you start
Open the project from the Projects list. Every member of the organization, including a Viewer, sees the entries.
The three entries
Under Work on this project, the screen says "Each product checks your access when you arrive. A link here is not a permission." and lists:
| Entry | The screen describes it as |
|---|---|
| Develop in Workspace | "Open your own development environment, editor and preview." |
| Tasks and automation in Delegate | "Requests, reviews, approvals and delivery." |
| Applications in CDN | "The published applications and releases of this project." |
An entry that you can use has an Open button. When product records are already linked to the project, the entry also says how many, as in "2 linked here".
Open one
- Choose Open on the entry.
- You arrive in that product with the project in context. The product signs you in with your Beyond account if you have no session there yet: one login, no second password.
- The product decides what you see. It checks your access to its own resources, whatever Projects showed.
Expected outcome: the product opens on this project, or tells you in its own words why it cannot.
A link here is not a permission
Open carries the project identity and nothing else: no credential, no role, no grant. This has three consequences:
- Sending the link to someone gives them nothing. They need their own access in that product.
- A product may refuse you although Projects showed Open. Projects cannot see a product's permissions.
- For Workspace, the missing Open button is only a courtesy. Workspace applies the closed development access itself, together with your membership and your permission on the project, and answers with a screen of its own for each case.
In CDN you land on the applications of the organization, filtered to the project: see The applications of a Beyond project. In a Delegate installation that is connected to Beyond Projects, Delegate opens the attached project, lists several, or offers an administrator the form that attaches a repository: see Use Delegate with a Beyond project. A Delegate without that connection opens as usual.
When an entry has no Open button
The entry says why instead of offering a dead link:
| The entry says | Meaning | What to do |
|---|---|---|
| "Not configured in this installation." | This installation has no address for that product | Nothing you can change. The people who run the installation configure it |
| "Not available while the project is archived or deleted." | All three entries close while the project is not active | Restore the project, if your role allows it |
| "You do not have Workspace development access in this organization." | Only on Develop in Workspace: the organization is not enabled, or you were not selected | Read Closed access to Workspace development. The other two entries still work |
Limits
- Projects has no publish action, and neither does Workspace. Applications in CDN leads to applications and releases that were prepared through the CDN.
- What happens after Open on Develop in Workspace, including every refusal screen, is in Open a project in Workspace.
Next action
Developing? Open a project in Workspace. Delivering applications? The applications of a Beyond project. Working with requests and agents? Use Delegate with a Beyond project.