Organizations
Organizations model teams, companies, and communities in Bosca—bringing membership, permissions, and signup policies together.
Organizations represent your team, company, or community inside Bosca. They bring together people, access, and onboarding so you can confidently control who sees what—and how new members join.
What Organizations let you do:
- Create a home for your team or community with a clear public profile
- Manage membership with simple roles (for example: Administrators and Users)
- Set clear permissions for content, workflows, and administration
- Choose how people join: by email domain, invite list, or shareable tokens
Why it matters:
- Keep projects and content neatly scoped to the right audience
- Make onboarding fast and secure—auto‑join for your domain, invites for guests
- Align governance with your organization’s policies while staying easy to run
Key ideas:
- Organization profile: Each organization has a profile (name, details, visibility) that powers discovery and listings.
- Membership: People join an organization and get access through groups like Administrators and Users.
- Permissions: Decide who can view, edit, manage, or publish across Collections, Metadata, and Workflows.
- Visibility: Control how your organization appears internally and publicly.
Flexible ways to join:
- Email domains: Specify one or more domains. Enable auto‑join and pick a default group so verified users can join without friction.
- Allow list: Approve specific email addresses ahead of time and choose the group they’ll join.
- Invite tokens: Share tokens that map to different groups for controlled onboarding.
How Organizations relate to Profiles:
- Organizations are built on top of profiles, so they benefit from the same personalization and analytics described in Profiles and Analytics.
- As activity grows, you can tailor content, recommendations, and workflows to each organization’s needs.
Common examples:
- Auto‑join anyone with @yourdomain.com into the Users group
- Share an admin invite token to onboard a project lead with elevated permissions
- Keep partner organizations separate, each with its own membership and content scope
Related guides:
- Security and Groups: see Architecture / Security
- Profiles overview: see Profiles
- Analytics signals: see Analytics