Workspaces, access, and invitations
Who sees what, invites, and activation.
Last updated: May 2026
Workspaces
Fulreach organises LinkedIn accounts, campaigns, and related data inside workspaces. You need membership on a workspace before you can work with its accounts—members do not implicitly see every workspace in the broader platform.
Think of workspaces as bounded areas for outbound: each has its own Connected LinkedIn identities, campaigns scoped to chosen accounts.
Invite-only access (Fulreach tenants)
Fulreach onboarding is designed around organisation owners issuing platform invites to trusted emails:
- Sign in with that exact email.
- Activation may depend on completing Stripe checkout/billing, depending on your tenant configuration.
- Activation grants app access for Fulreach (application-level entitlement)—you can then operate within allowed workspaces according to membership + role.
Consult your Fulreach administrator if you are unpaid or revoked and expect access—you may be blocked intentionally until lifecycle states move forward (pending invite → checkout → activated).
App roles vs workspace roles
Fulreach differentiates scopes:
Application scope (user_apps style access)
Fulreach stores an Owner / Admin / Member style role at platform level guiding high-level entitlement (organisation ownership capabilities, Stripe invite admin paths, onboarding upserts)—see Roles and workspace access.
Workspace scope
Within a workspace Fulreach distinguishes workspace members carrying another Owner / Admin / Member matrix—distinct meaning from app labels but reused names historically: workspace admin can reshape workspace artefacts (accounts moves, edits) versus member narrower visibility documented in Fulreach internals.
Until your organisation adopts a clarified single terminology in-product, mentally separate:
- “Can I administer billing & invites?” → app owner paths (plus platform invite tooling).
- “Which LinkedIn workspaces do I collaborate in?” → workspace membership.
Troubleshooting invites
Invited identity mismatch (Google workspace email alias vs Stripe email) triggers activation quirks—prefer one canonical email organisation-wide.
If invite shows paid yet product still denies access confirm webhook reconciliation & support channel.