# Organizations, brands and team access > Understand workspace structure, invite teammates, and choose the access each person needs. Canonical URL: https://pollenate.dev/docs/workspace/organizations-and-brands/ An **organization** owns the workspace, billing, members and API keys. A **brand** groups related inboxes and forms and supplies their visual identity. Use separate brands when products or teams need different presentation or access. ## Create and select a brand Open **Brands**, create a brand and give it a clear name. Select it before creating an inbox or form. The brand editor supports a logo, colors, font and corner style; [Brand and widget themes](/docs/workspace/themes/) explains how those settings reach public collection surfaces. Changing the selected brand changes which resources you are working with. If a resource appears missing, check both the organization selector and brand selection before recreating it. ## Invite teammates Use **Settings → Invitations** for email invitations or **Settings → Invite Links** for a reusable join link. Invite links can carry a role, brand access, expiry, maximum uses and an active/inactive setting. Review those settings before sharing the link. Organization roles include owner, admin, member, billing and viewer. Available actions also depend on permission overrides and brand membership; a role name alone does not describe every resource a person can access. Owners and other authorized administrators can review permissions in Settings. A member with permission to manage their own forms can create and maintain those forms without receiving broad management access. **Private form sharing** adds a separate visibility rule: see [Private forms and recovery](/docs/forms/private-sharing/). ## Domain-based joining An authorized administrator can verify an organization domain under **Settings → Domains**. The interface provides the verification method and value to publish. Once verified, people with matching email addresses can find the organization during onboarding and request access. A matching domain is an access-request workflow, not an invitation to assume that every address is already a member. ## Account security Use the profile and security controls to manage your personal account, passkeys and two-factor authentication. Organization administrators can enforce two-factor requirements where their permissions allow it. These controls do not replace reviewing a person's role and brand access. For software integrations, choose the correct [authentication method](/docs/api/authentication/): an organization key, a personal key or a connected app has different access behavior. Do not share a teammate's login credentials to connect an integration.