Workspace roles
The current workspace member model uses three roles:
The exact content action available to a person can also depend on plan, post state, connected-account capability, and the backend function being used. Do not treat a static role table as a bypass around those checks.
Invite a member
Owners and admins can send a workspace invitation from Settings → Workspace.1
Enter the email
Enter the email address that should receive access.
2
Choose Admin or Member
The ordinary invite flow supports Admin or Member. It does not let the caller assign the Owner role.
3
Send the invitation
Socializioz verifies the caller’s workspace membership and role before creating the invitation.
The invitee does not need to exist yet
The current invite backend supports email-only pending invitations.- If the email already belongs to a Socializioz user, Socializioz can associate that user with the invitation and create an in-app invitation notification.
- If the person has not signed up yet, the invitation can remain pending for that email until they create an account with the invited address and complete the supported acceptance flow.
Duplicate invitations
Socializioz checks for an existing member and for an already-pending invitation before creating another pending invite for the same workspace/email. If an invite is already pending, the workflow can return that existing state rather than intentionally creating duplicates.Pending invitations
Owners/admins can review pending invitations from Workspace settings. The current UI shows the invited email, requested role, and pending state. Authorized managers can revoke an invitation that should no longer remain active. The backend invitation record has its own expiry/lifecycle; use the state shown by Socializioz rather than assuming an old emailed link remains valid indefinitely.Manage members
The member-management backend re-checks the caller’s role and target workspace before a role update or removal.Change a role
Eligible members can be changed between Admin and Member by an authorized workspace manager. The Owner role is protected and is not available in the ordinary member role selector.Remove a member
Owners/admins can remove eligible non-owner members. The protected Owner record cannot be removed through the normal member-removal action. A removed user loses the membership that granted access to that workspace. Re-access requires a valid membership/invitation again.Owner changes
The current product UI does not expose a normal “make this person Owner” control in the member selector. This documentation does not promise a specific automated ownership-transfer process or guaranteed support outcome. If an ownership change is required, contact Support with the workspace and requested change so the currently supported procedure can be confirmed.Approval workflows
Approvals let a team put a review step between content preparation and publishing. A typical flow is:- A creator prepares the post in Composer.
- The post is submitted for review instead of being treated as published.
- An authorized reviewer inspects content, media, destination, timing, and current validation state.
- The post is approved or rejected through the current approval workflow.
- Scheduling/publishing still has to pass the normal account, plan, media, timing, and provider checks.
Separate workspaces for separate clients or brands
When different clients or business units should not share operational context, use separate workspaces. Workspace-scoped areas include important publishing records such as:- Posts and schedules.
- Campaigns.
- Media assets.
- Social publishing accounts.
- Workspace brand context.
- Membership.
Review team activity
Use Activity log to inspect supported recorded workspace events, and use the record’s owning surface—Publishing Hub, Connections, Campaigns, etc.—to confirm its current state. The Activity log is not documented as a complete immutable audit ledger of every possible user action unless that event is actually recorded by the current backend.Security practices for teams
- Invite only the people who need workspace access.
- Use Member rather than Admin when settings/member management is not required.
- Revoke stale pending invitations.
- Remove memberships when access is no longer needed.
- Keep client work in the correct workspace.
- Use approval workflows for consequential content when available.
- Never share provider tokens or Socializioz session credentials as a shortcut for collaboration.