Organizations & Teams
The platform groups users and their resources into organizations. Organizations replace traditional "teams" and provide the primary unit of collaboration, billing, and access control.
Organizations
How Organizations Work
Organizations are the core boundary in the platform. Every user belongs to an organization, and resources are scoped to the user's organization.
Organization Properties:
- Name and description: Identifies the organization
- Owner: The user who created the organization (has full control)
- Admin IDs: Additional users with administrative privileges
- Billing email: Used for billing notifications and invoices
- Credits: Balance, lifetime usage, alert thresholds and credit grants (only when billing is enabled)
- Settings: Timezone, currency, fiscal year start
- Status: Active or inactive
Organization Types
Solo Organizations:
- Created automatically for every self-registered user (via password or Google OAuth)
- The user is both owner and sole member
Team Organizations:
- Created explicitly through the register-with-new-organization flow
- Support multiple members with different roles
- Members can share resources within the organization
Who Sees Whom and What
- All users see all other users
- Resources are accessible across users (subject to sharing permissions)
- New self-registered users require admin approval before they can log in
On Strongly Cloud, users see only members of their own organization, resources are filtered by organization, and someone alone in their organization cannot share with anyone.
Organization Members
Member Roles
Each member has an organization-level role:
| Organization Role | Capabilities |
|---|---|
| Owner | Full control over the organization, billing, and all members |
| Admin | Manage members and organization settings |
| Member | Access shared resources within the organization |
| Viewer | Read-only access to shared resources within the organization |
Organization roles are separate from platform roles (admin, developer, app). A user has both:
- A platform role that determines which UI features they can access
- An organization role that determines their permissions within their organization
Inviting Members
Members are invited to organizations through the invitation system:
- An existing member (with invite permissions) creates an invitation
- The invitation is stored with:
- Target email address
- Organization ID
- Assigned role (admin, member, or viewer)
- Invitation token and expiration date
- Status (pending, accepted, expired, or revoked)
- The invited user receives the invitation (via email or shared link)
- The user registers using
users.registerWithInvitationwith the invitation token - The system verifies:
- The invitation token is valid and not expired
- The email matches the invitation email
- The email is not already registered
- On success:
- A new user account is created with the app platform role
- The user is added to the organization with the invitation's role
- The invitation status is updated to "accepted"
Member Management
Each organization member record tracks:
- Which organization the member belongs to
- The member's organization role (owner, admin, member, viewer)
- Membership status (active, pending, suspended, or removed)
- Who invited the member and when they joined
- Whether the member's resources have been transferred or deleted (for offboarding)
Resource Sharing
How Resource Access Works
Every resource is reached through its owner, its sharing and its organization. On Strongly Cloud, every resource query is filtered to the user's organization, for all resource types (apps, workflows, data sources, etc.), so members of one organization never see another organization's resources.
Sharing Within an Organization
Within an organization, users can share resources with other members:
- The share picker lists all active organization members (excluding yourself)
- Share targets are verified to be in the same organization; targets outside it are rejected
- Archived users are never listed in a user picker (sharing, owner, reviewer, collaborator, assignee or scope pickers), and sharing with or reassigning to an archived user is refused
- Shared resources inherit the organization's access boundary
Resource Ownership
Resources in the platform have an owner:
- The owner is the user who created the resource
- Admins can access all resources regardless of ownership
- When a user is archived or removed from the organization, the administrator chooses what happens to everything they own, Library records and agent primitives included: transferred, deleted, or (archiving) left as it is. See User Lifecycle & Offboarding
- Organization-scoped resources persist even if the creating member leaves
User Visibility
Who Can See Whom
- All users can see all other users
- Admin users can additionally see full user details
On Strongly Cloud, users see only members of their own organization, and someone alone in their organization sees only themselves.
Best Practices
Organization Structure
- One organization per team or company: Keep related users in the same organization for easy resource sharing
- Use organization roles appropriately: Only grant owner/admin to users who need to manage the organization
- Regular member review: Remove inactive members and review roles periodically
Resource Management
- Ownership clarity: Ensure critical resources are not owned by a single user who might leave
- Naming conventions: Use consistent naming for resources to help organization members find them
- Clean up on departure: When a member leaves, transfer their critical resources before removing them
Security
- Invitation security: Invitation tokens have expiration dates to prevent stale invitations
- Email verification: Invitation emails must match the registered email
- Organization isolation: On Strongly Cloud, resources are strictly isolated between organizations
- Offboarding: Track artifact transfer and deletion status for departing members
A user's organization role (owner, admin, member, viewer) controls their permissions within their organization. Their platform role (admin, developer, app) controls which features they can access in the UI. Both work together to determine overall access.