Settings is the configuration hub for your Socializioz account and active workspace. On desktop it is hosted inside the Workspace shell; on mobile it opens as the mobile Settings experience.
Connections are intentionally a first-class Socializioz destination rather than a full settings subsection. Older deep links to the integrations tab are preserved, but the current interface points users to the Connections hub.
Current Settings areas
The current Settings experience includes:
The visible desktop navigation groups these into Account, Workspace, Preferences, and Support sections. Mobile presents the same settings through a touch-oriented menu.
Profile
Profile is the canonical place for user-level account preferences such as the saved timezone.
Your timezone affects how Socializioz displays dates and times across scheduling and other time-aware surfaces. Changing the display timezone does not rewrite a previously scheduled UTC instant into a new scheduled time.
Notification quiet hours use this saved timezone rather than maintaining a second independent timezone setting.
Use the Profile/session control to log out from the current Socializioz experience. For security guidance, see Account security.
Workspace name and description
The Workspace area exposes the active workspace name and optional description.
Only workspace Owner or Admin roles can edit these fields. The frontend sends only the intended name/description change; the backend re-checks workspace membership and role before saving whitelisted fields.
When both fields are changed, use Save Changes to persist them.
Workspace identity and Brand Command
The Workspace area also shows the canonical brand identity associated with the active workspace.
Depending on current state, authorized users can:
- Open the existing Brand Kit/Brand Command.
- Create the workspace brand profile when none exists.
- Scan a website to help prepare brand context.
- Review brand completeness.
The current workspace identity is designed as one canonical brand context for the workspace, rather than a loosely selected list of unrelated profiles.
See Brand Command for the full workflow.
Members and invitations
Workspace membership is backend-mediated.
The current workspace member section uses these roles:
Owners and admins can manage the current roster and invitations through permission-checked backend functions.
Invite a member
Owners/admins can:
- Enter an email address.
- Choose Admin or Member.
- Send the invitation.
The invite can remain pending when the person has not signed up yet. If the email already belongs to a Socializioz user, the user can receive the workspace invitation through the supported invitation flow.
Duplicate pending invitations are handled rather than intentionally creating unlimited duplicate rows.
Pending invitations
Owners/admins can review pending invitations and revoke an invitation that should no longer remain active.
Change a member role
An authorized Owner/Admin can change eligible members between Admin and Member. The Owner role is protected by the backend workflow rather than being assignable through the ordinary role selector.
Remove a member
Eligible non-owner members can be removed by an authorized workspace manager. The backend re-checks the caller role, target workspace, and protected-owner rules.
See Team collaboration for collaboration and approval workflows.
Connections shortcut
The old Settings integrations location is no longer the primary management surface.
Use Connections for:
- Social Channels.
- Connection health.
- Reconnect/disconnect management.
- Supported Apps & Data when they are released to your account.
- AI/MCP connection surfaces when available.
The Settings integrations compatibility section exists to point users toward that canonical hub, not to duplicate connection management.
Notifications
The current Notification Settings interface exposes only controls that have working product behavior.
It includes:
- Master notification enable/disable.
- In-app notifications.
- Email notifications.
- Current event categories.
- Email quiet hours.
Browser push, digest selectors, and engagement-milestone switches are intentionally not exposed in the current interface because their full user-facing pipelines are not active.
See Notifications.
Billing
Billing is rendered through the existing Socializioz Billing experience and is reachable from the Settings/Workspace shell and supported deep links.
Use it to review the active plan, available checkout/change controls, usage, and available invoice information.
See Plans and billing for the current published plan matrix.
Refer & Earn
Refer & Earn is the user-facing entry point to the Socializioz Partner Program.
Depending on the current partner state, this area can let you:
- Review and accept the current Partner Terms.
- Choose Join Partner Program.
- See pending, active, rejected, or blocked partner status.
- Copy Your Referral Link after approval.
- Review Earnings Overview, Pending Payout, Paid to Date, Your Stats, and Recent Referrals.
- Open the full Partner Dashboard.
Partner/referral records are separate from workspace content and from your own subscription entitlement. Joining the partner program does not automatically change your Socializioz plan.
See Refer & Earn and Partner program.
Privacy & Terms
The legal settings area links to current policy surfaces. Product documentation is not a substitute for the legally controlling policy text.
See Privacy and data management.
Language
Socializioz supports the current application languages exposed by the Language settings control, including English and Arabic/RTL behavior.
Changing language updates the interface preference. Exact visual mirroring is owned by each current responsive surface, so this guide does not promise that every panel always moves to a particular side when designs are revised.
Support
Settings includes the current AI-first Support experience. Use it for product, publishing, connection, billing, or account issues and escalate through the supported human-review flow when needed.
See Support.
Leave a workspace
A non-owner workspace member can use Leave Workspace from the workspace danger area.
Leaving removes the user’s access to that workspace. If another eligible workspace is available, Socializioz can move the user toward that workspace; otherwise the user can be routed back through the appropriate workspace/onboarding path.
Review any work you still need before leaving. Regaining access requires a new eligible membership/invitation.
Delete a workspace
The current danger area exposes Delete Workspace only for the workspace Owner.
The confirmation flow requires typing the workspace name before the delete action becomes available. Deleting a workspace starts a 7-day recovery period rather than immediately purging the workspace.
During this recovery window, the workspace is treated as deletion-pending and ordinary product access to it is blocked. An eligible restore can return the workspace before final purge.
After the 7-day recovery window expires and final purge occurs, the deleted workspace cannot be restored. Do not use deletion as a troubleshooting step. Export or preserve anything you need first and confirm the correct workspace before proceeding.
Delete your account
Delete account is a separate account-level lifecycle from deleting one workspace.
Account deletion also enters a 7-day recovery period before final purge. Normal product access is blocked while the account is deletion-pending, and an eligible recovery can return the account to active status during that window.
After the recovery window expires and final purge occurs, the deletion is irreversible. Some records can still be retained when required for billing, tax, fraud prevention, disputes, security, legal, or regulatory obligations.
Use the confirmation presented by Socializioz and review Privacy and data management before proceeding.
Workspace isolation
Workspace-scoped product data must resolve against the active/authorized workspace before being accessed or changed.
Important workspace-scoped areas include posts, campaigns, assets, social publishing destinations, workspace brand context, and membership. Some preferences, such as a user’s language/timezone/notification settings, belong to the user rather than being duplicated per workspace.
For integrations, the scope can differ by integration type. For example, current Google Calendar/Sheets connector identity is user-level rather than a workspace publishing identity, while social publishing destinations are workspace-scoped. See Integrations instead of assuming every connector shares the same ownership model.
Troubleshooting
