Team Hacks: Using Your Account With Your Team

Allowing for multiple users to access a SmarterQueue account is something that we know is important for many of our users.

Currently, there are separate workaround hacks that would still give you a similar end result and let you delegate your SmarterQueue workflow, until Teams feature is released. 

In This Article

Connected Accounts

If you have connected your Twitter and/or Instagram account to SmarterQueue. You can allow any user to login through either of these options. 

SmarterQueue Credentials

You can share your SmarterQueue Username and Password details and they can access through this method. We recommend using a secure password vault.

What Access Will They Have?

Once logged in, they'll have access to all of the accounts.

In the near future, we plan to build full team features, where you'll be able to create separate logins and set permissions for each team member. 

I Don’t Want My Team To Access My Social Profiles

Completely understand. 

We recently added security features that let you limit which social profiles can be used for login. 

You'll find more details in Settings > Login Security. You can lock down your account so that only your personal social profiles can be used to log in, or you can even disable all social profiles and only allow login with your email and password.

I Want To Approve All Content

This is a big aspect of our Team Collaboration feature we are looking into and understand the appeal.

In the meantime, a workaround would be for your team to create posts without scheduling, leaving you to go into SmarterQueue to approve and quickly schedule.

You can best let us know about your interest in this feature through our Feature Request Board. Here you can vote on this specific feature as well as any others that may benefit your journey with us. ⬆️

You can also check our Roadmap and Release Dates and see that we are working on adding this functionality to SmarterQueue.

Did this answer your question? Thanks for the feedback 💫 There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us