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.
- Availability: Experimental
- Evidence: Recorded run
- Explanation
The problem this solves
You signed in, you are a member of your organization, perhaps even its Owner, and Projects still says you cannot develop in Workspace. That is the expected answer for almost everyone today: development in Workspace is closed, and neither signing in nor membership opens it.
Four things are needed, and you control none of the first two
| What | Who decides |
|---|---|
| 1. Workspace development is enabled for your organization | Beyond |
| 2. You are selected, individually, among its members | Beyond |
| 3. You are a current member of that organization | An Owner or Administrator of the organization, in Beyond Accounts |
| 4. You have permission on the project in Workspace | Workspace |
All four are needed at the moment you use them. Enabling an organization admits nobody by itself, and selecting a person who is not a member admits nobody either.
What does not give access
- Joining a waitlist.
- Signing in, or having a Beyond account.
- Being invited to an organization, or being a member of it, with any role.
- Having a link to a project or to Workspace.
An Owner cannot enable their own organization or select their own members. There is no button for it and no request form in Projects.
How an organization asks
An Owner or Administrator can tell Beyond that the organization is interested: in CDN administration, the waitlist form has the checkbox Development in Workspace (closed access). See Asking for Workspace development.
Asking enables nothing. Beyond reviews the request and, if it approves, enables the organization and selects its members separately, one by one. An approved request whose members were not selected still leaves everyone in the second state below.
The three states you can see
The organization panel in Projects has a Workspace development box with exactly one of these sentences:
| The sentence | What it means | What you can do |
|---|---|---|
| "You can develop in Workspace in this organization." | The organization is enabled and you are selected | With a role that can create, create a project. Open a project in Workspace |
| "Workspace development is enabled for this organization, and you have not been selected to use it. Beyond selects each member individually." | Beyond enabled your organization and selected other people, or nobody yet | Everything that does not need development: see projects, open them in Delegate or CDN |
| "Workspace development is not enabled for this organization. Access is closed and is granted by Beyond: joining the waitlist, signing in or being a member does not enable it." | Beyond has not enabled your organization | The same |
The standing is per organization. If you belong to several, change the Organization in the header to see each one.
What changes without development access
- New project is absent, and the list says "Creating a project needs Workspace development access and a role that can create projects."
- On a project, Develop in Workspace has no Open button and says "You do not have Workspace development access in this organization."
- Nothing else changes. You still see the projects of your organization, and with the right role you can register an existing project, rename, archive and restore.
Workspace checks again by itself when someone arrives, and while they work. Hiding the button in Projects is a courtesy, not the lock. In Workspace the refusal reads "Workspace development is not enabled for you here": see When you do not get in.
If access is withdrawn
Beyond can withdraw a selection or disable an organization. Development stops being available at once. No project, source or work is deleted by it, and the projects stay in your list.
This is not a CDN plan
Workspace development access is separate from everything in the CDN. The request travels on the CDN waitlist only because that is where an organization already asks Beyond for things. Enabling Workspace changes no CDN plan, no premium capability and no credit, and approving a premium request does not enable Workspace.
Next action
Not sure why you cannot create a project? I cannot create a project separates the role from the access.