Organizations
Group members, maintain an organization profile, and configure signup and access rules.
Organizations and access boundaries
An organization groups members and has a linked Profile for its identity. Its record has a name, JSON attributes, system attributes, visibility, and a profile ID.
Bosca is effectively single-tenant. An organization does not create an isolated tenant or automatically scope content visibility. Collections, metadata, and other entities keep their own access rules. Use group-based permissions to grant access to those entities.
List organizations
organizations.all returns records for administrators and an empty list otherwise. A single organization lookup checks VIEW permission. Management fields such as signup configuration, permissions, and member lists require additional authority. GraphQL exposes the associated profile object; profileId is a Kotlin model property.
Create an organization
OrganizationInput requires name, attributes, systemAttributes, visibility, domains, signupEmails, and signupTokens. Empty arrays are valid for the signup lists. Its optional id identifies an existing organization when editing. ProfileInput supplies the associated name, attributes, and visibility.
The creation resolver is intentionally available to signup flows without a caller authentication parameter. Edits, deletion, and membership management have their own permission checks.
Membership and groups
Membership records link an organization ID and a principal ID. The profile API exposes these organizations for profiles linked to that principal. Organization creation also establishes administrator and user groups for its signup and permission configuration.
Membership and group grants are separate records. Adding a member directly does not assign a signup group. Removing the membership record does not revoke its existing security-group memberships. Manage those memberships explicitly when changing access.
Both membership mutations require MANAGE permission on the organization.
Signup mechanisms
- Signup tokens: share a token that selects an organization signup group. Creating or deleting a token requires organization
MANAGEpermission. - Signup emails: preconfigure an email address and signup group type. These mutations require administrator authority.
- Domains: configure a matching email domain,
autoJoin, and a default group. Adding or removing domains requires administrator authority.
Signup group types are ADMINISTRATORS, USERS, and UNKNOWN. They select the organization's groups, not the platform-wide administrator role.
For an ordinary member invitation, supply { "type": "USERS" } as the token variable. Read the generated token from the returned signupTokens list.
Organization permissions
OrganizationPermission grants an action to a security group on the organization record. It does not grant that action on every item associated with a member or the organization. The organization permission evaluator maps API-token access to profile scopes such as profiles:read and profiles:manage.
Where to look in the workspace
Models live in social/core-profile. Membership, signup, and resolver behavior live in social/profile, alongside src/main/resources/graphql/organizations.graphqls.