Beyond Workspace and Projects

One project across the products#

A team that builds with Beyond uses more than one product: it develops in Workspace, runs requests and automation in Delegate, and delivers published applications through the CDN. Without a common record, the same piece of work would be registered three times under three names.

Beyond Projects is the place where that work is created once. It shows, on one screen:

• the organizations you belong to and your role in each;
• the projects of the organization you are working in;
• for each project, the way into Workspace, Delegate and CDN.

You sign in with your Beyond account, the same one you use everywhere else. See Sign in to Beyond Projects.

What a project is#

A project is one stable identity that belongs to one organization.

• Its identity looks like prj_0f3c9a1b2d4e5f6071829304: prj_ followed by 24 lowercase hexadecimal characters. It is the same in Workspace, Delegate and CDN, it never changes and it is never used again for another project.
• Its name is for people. You can rename a project; its identity stays.
• It belongs to exactly one organization, and only members of that organization can see it.

A project is not a repository, a package or a CDN application. Those belong to the products, and one project can have several of them: several repositories attached in Delegate, or several applications in CDN. Projects never assumes there is exactly one.

The canonical explanation is Project, organization and account.

Who decides what#

This is why a link from Projects into a product is never a permission: "Each product checks your access when you arrive. A link here is not a permission."

Development in Workspace is closed#

Opening a development environment in Workspace is not available to everyone who signs in. Beyond enables Workspace for an organization and selects each member individually. Joining a waitlist, being invited or being a member does not give access. Closed access to Workspace development explains the three states you can see and what each one means.

You can still sign in to Projects, see your organizations and projects, and open a project in Delegate or CDN without development access.

Develop in Workspace#

With development access, a project opens in your own environment of it, where you edit files, work with Codex, review and integrate changes and look at the preview. The Workspace client ran against a real local administration for its main journey, and against a fixture of the services for everything else; every page says which of its behaviors ran against which.

• Open a project in Workspace: arriving, each refusal, your environment and its stages.
• Edit files, work with Codex and review and integrate changes.
• Preview your work and share it, and choose what you develop.
• On a phone and the desktop app.

Integrating is not publishing: see Preview, integration and publication are different things.

What does not exist#

Where to go next#

• Sign in to Beyond Projects — Sign in to Beyond Projects with your Beyond account, choose the organization you are working in, and read the three parts of the screen.
• Closed access to Workspace development — Development in Workspace is closed. Beyond enables it for an organization and selects each member individually, and both are needed. What the three states on your screen mean and what does not give access.
• Organizations and members — Beyond Projects shows your organizations and your role. Creating an organization, inviting people and managing members happen in Beyond Accounts, and you come back to Projects when you are done.
• Create a project from the Beyond template — Create a project in Beyond Projects from a template version you choose. The version is recorded with the project, and the project receives the identity that Workspace, Delegate and CDN share.
• Register an existing project — Give work that already exists in Delegate or CDN one project identity in Beyond Projects, without a template, without development access and without changing anything in those products.
• 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.
• Rename, archive, restore and delete a project — What each project action in Beyond Projects does, who can use it, and what it never does. Archiving and deleting remove nothing in Workspace, Delegate or CDN.
• 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.
• Open a project in Workspace — Arrive in Beyond Workspace from Projects, sign in, understand each way of not getting in, and start, stop and come back to your own development environment of the project.
• Edit files in Workspace — Open files in tabs, let autosave write them or save at once, know what saved means, resolve a conflict when Codex or someone else changed the file, and keep unsaved drafts across devices.
• Work with Codex in Workspace — Start a personal conversation, steer or interrupt a run, understand the one running conversation per environment, connect your own provider account and read usage. Running Codex inside an environment has not been validated.
• Review and integrate changes — Read the three numbers of your working copy, make a checkpoint, bring in what others integrated, review the diff, the verification and the conflicts, and integrate. Integration is not publication, and there is no Publish action.
• Preview your work and share it — See the preview of your environment, choose who can see it, create and revoke visitor links, and know what a visitor can and cannot do. A stopped environment has no preview, and nobody starts it by looking.
• Packages, modules and what you develop — Read the packages and public modules Workspace detected, see which build, choose explicitly what is in development, and create files, modules and packages with the assistants. Page, widget and layout assistants are not available.
• Workspace on a phone — What Workspace offers on a phone or a small touch screen. You read conversations and the review, edit text with the same save and conflict rules, and compare with a linear diff. The full desktop editor is not loaded there.
• The Workspace desktop app — What the Workspace desktop app is, how it differs from Workspace in a browser, and what has and has not been run. It was only smoke-run and has never been used for a real sign-in.
• Troubleshooting Beyond Projects — Start from what Beyond Projects or Workspace shows you. You cannot create a project, you have no development access, Projects cannot answer, someone changed the project, your environment did not start, the preview is unavailable, another conversation is running, or your changes conflict.

Developing the project itself? The project template explains what a new project contains.