Topic 10
How Teams and Workspaces Stay Organized
Jena4 gives each person an organization-wide role, while workspaces keep Development, Staging, Production, or other operating contexts distinct.
One team, three contexts
The people may be the same. The work should not be mixed together.
A new Jena4 account begins with an organization and a Development workspace. As the company grows into Staging and Production, workspaces keep each context’s decisions, supporting information, connection credentials, and notification setup organized separately, while the organization’s team and role structure remains consistent.
How people enter
Access begins with the intended person—not a shared password.
An owner or administrator invites someone into an allowed role. Owner access is not assigned by invitation, and administrators cannot grant administrator access.
The invitation must be accepted by the invited email address within seven days.
Jena4 sends an eight-digit code or secure link. A link requires an explicit confirmation before sign-in completes.
Signup and invitation requests include a security check. If that check cannot be confirmed, Jena4 blocks the request and makes clear that no email was sent.
Four organization roles
Administrative control, contribution, and review remain distinct.
- Owner
Holds protected organization control and cannot be changed or removed through the current team controls.
- Administrator
Manages team access and settings, but cannot manage another administrator or grant administrator access.
- Member
Creates and maintains governed decisions and their supporting information.
- Viewer
Reviews the organization’s governed information without changing it.
People cannot change or remove their own membership through these controls. Those guardrails reduce accidental loss of access or unintended elevation of authority.
What a workspace separates
Workspaces organize operating contexts. They are not separate membership silos.
Governed decisions, supporting information, connection credentials, and notification configuration remain attached to the relevant context.
An organization member’s role applies across its workspaces rather than changing separately for Development, Staging, or Production.
A current boundary
One person currently belongs to one customer organization.
Jena4 does not currently support the same account belonging to multiple customer organizations. Teams should plan invitations and account ownership around that present boundary.