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.
- Availability: Experimental
- Evidence: Recorded run
- How-to guide
Before you start
You must be signed in to Beyond Projects. To invite people or change roles you must be Owner or Administrator of the organization in Beyond Accounts; other members see the list there and cannot change it.
What Projects shows
The organization panel shows the organization you are working in and Your role: Owner, Administrator, Developer or Viewer. The role comes from Beyond Accounts. Projects keeps no member list of its own and cannot change one.
Under it, the sentence "Organizations and members are managed in Beyond Accounts. You will return here when you are done." is followed by four links:
| Link | Opens in Beyond Accounts |
|---|---|
| Members | The members of this organization |
| Invitations | Its invitations |
| Organization settings | Its settings |
| New organization | The form that creates an organization |
If the panel says "Organization management is not configured in this installation.", the links are absent. Open Beyond Accounts yourself and use Organizations, members, roles and invitations.
Manage members and come back
- In Projects, choose Members, Invitations, Organization settings or New organization.
- You arrive in Beyond Accounts, at that part of the organization. Accounts asks you to sign in only if you are not signed in there.
- Do the work in Accounts. Every step, rule and message is in Organizations, members, roles and invitations: creating an organization, inviting with a one-time link, changing a role, removing a member.
- Choose Return to Projects. Accounts shows it at the top of the screen while you are there, and again in the confirmation after a completed change.
Expected outcome: you are back in Projects and it says "Your organizations were read again from Beyond Accounts." A new organization appears in the Organization selector, and a changed role is the one shown as Your role.
What your role lets you do in Projects
| Owner | Administrator | Developer | Viewer | |
|---|---|---|---|---|
| See the projects of the organization | Yes | Yes | Yes | Yes |
| Create a project from a template | Yes, with development access | Yes, with development access | Yes, with development access | No |
| Register an existing project | Yes | Yes | No | No |
| Rename, archive and restore | Yes | Yes | No | No |
| Delete a project | Yes | No | No | No |
Projects shows only the actions your role allows, and explains a missing one beside it instead of offering a button that would fail.
A role is not access to a product's resources
A role in an organization answers one question: what you may do with the organization's projects in Beyond Projects. It is not:
- Workspace development access. An Owner without it cannot create a project from a template or open a development environment. See Closed access to Workspace development.
- A seat, a role or project access in Delegate. Delegate invites people to its own workspaces and grants access per project.
- A CDN plan, credit or capability.
Each product checks your access to its own resources every time you arrive. Identity and resource permissions explains who decides what.
Limits
- Removing someone from the organization in Accounts removes the organization and its projects from their Projects screen. It deletes no project and no work.
- Projects cannot invite, remove or change a role, even for an Owner. Those actions exist only in Accounts.
- Accounts sends no invitation message: you deliver the invitation link yourself. See Invite someone.
Next action
Invited your team? Check who has Workspace development access, then create a project.