Control who can access the creator sales operation
Queux separates creator ownership, setter permissions and third-party connections. Creators decide who joins the team and what they can access, while Meta, Google and Stripe handle authentication for their own services.
Queux uses role-based team access and provider-authorised integrations instead of requiring creators to share social or calendar passwords with setters. Creators can grant or revoke team access, while Stripe handles payout identity verification and sensitive bank details.
No password sharing
Setters use their own Queux account and granted permissions.
Revocable access
Creators can remove a team member or disconnect an integration.
Stripe-hosted verification
Stripe handles setter identity and payout account onboarding.
Separate accounts and explicit team access
A setter joins Queux with their own account. The creator invites or accepts that person into a team relationship and chooses the access appropriate to their work. This is different from giving a contractor the creator's login credentials.
Creators can control inbox and calendar access and can remove a setter from the team. Removing access does not require changing a password shared across the wider business because the setter's identity and permissions are separate.
How connected accounts are handled
- 01
Authorise the provider
The relevant account owner completes the Meta, Google or Stripe connection through that provider's authentication flow.
- 02
Use scoped functionality
Queux uses the connection for its stated workflow, such as supported messages, calendar availability or payouts.
- 03
Grant team permissions
The creator decides which Queux team members may use inbox or calendar capabilities.
- 04
Revoke when needed
Remove the team member or disconnect the provider connection to stop future access.
Payments and sensitive financial details
Setter payout onboarding runs through Stripe Connect. Stripe performs its own identity checks and holds the bank information needed to deliver funds. Queux uses the resulting account and readiness status to determine whether an approved commission can be paid.
Queux does not ask creators to collect a setter's bank details directly. A failed or incomplete Stripe connection prevents the payment workflow and should be resolved by the setter through Stripe onboarding.
Related Queux workflows
Questions
No. Setters sign in to their own Queux account and use access granted through the creator's connected integration and team permissions.
Yes. A creator can remove a setter from the team and revoke their Queux access to the creator's workspace.
Stripe Connect handles identity verification and the sensitive payout account information required to pay a setter. Queux relies on Stripe's account status for payout readiness.
Run the social sales operation in one place
Bring the creator, setter, lead, booking and commission into the same workflow.