User Permissions
Levitate has four different user types that can be assigned, user by user. From least to most access to the platform and features— Limited User, User, Admin, and Super Admin.
Below is a handy table to lay out which features or functions each type of user can access while using Levitate!
| Feature or Function | Account Setting | Limited User | User | Admin | Super Admin |
| Send or post on behalf of other users | Editable | No | No | Yes | Yes |
| Create and Post blogs | Hard-coded | Yes | Yes | Yes | Yes |
| See Public Contacts | Hard-coded | Yes | Yes | Yes | Yes |
| Send to Public Contacts | Hard-coded | No | Yes | Yes | Yes |
| See Private Contacts | Hard-coded | No | No | No | Yes |
| Send to Private Contacts | Hard-coded | No | No | No | Yes |
| See Contact Owners and Connections | Hard-coded | No | Yes | Yes | Yes |
| See Archived Contacts | Hard-coded | No | No | No | Yes |
| View all scheduled content | Hard-coded | No | No | Yes | Yes |
| Key Date cards — Contacts I Own | Editable | Yes | Yes | Yes | Yes |
| Key Date cards — All Contacts | Editable | No | No | Yes | Yes |
| Birthdays | Editable | No | No | Yes | Yes |
| Create and Manage Automations | Editable | No | No | Yes | Yes |
| Schedule or Start Automations | Editable | Yes | Yes | Yes | Yes |
| Connect a Google Business Profile | Hard-coded | No | No | Yes | Yes |
| Reply to Google Reviews | Hard-coded | No | No | Yes | Yes |
| Create Surveys and Events | Hard-coded | No | No | Yes | Yes |
| Add to a Data Board (Donation, Policy, Opportunity) | Hard-coded | Yes | Yes | Yes | Yes |
| See all Opportunities | Editable | No | Yes | Yes | Yes |
| Access and Generate API Keys | Hard-coded | No | No | Yes | Yes |
| Add or Remove Tags from a Contact | Hard-coded | Yes | Yes | Yes | Yes |
| Completely Delete a Tag | Hard-coded | No | No | Yes | Yes |
Editable vs. Hard-coded
Editable features or functions are able to have their availability to different types of users updated or changed by your Success Specialist or our Support team. Hard-coded features or functions are not able to be updated by setting change.
FAQs
Q: How do I get editable features or functions edited?
A: Reach out to your Success Specialist or to our Support team. Not every feature is built equally— so some have more wiggle room for edits than others.
Q: Why are some contacts private and some public?
A: The status of a contact being private or public all depends on what you chose when initially setting up Levitate— if you chose to keep your contacts private, only you and connections to that contact (as well as Super Admins) will be able to see them. If you choose public, all users will be able to see them.
Q: What's a connection and how does it impact privacy?
A: A connection is generally a user on Levitate that has emailed the contact at least once. If each user chooses to keep their contacts private, a connection will still be able to see that contact and their timeline. Limited users can be limited to seeing only their correspondence with a certain contact or connection.
Connections can also be defined by roles brought over from an integration. Some integrations give multiple paths for contact ownership— for example, some insurance AMS systems allow a contact to have both a CSR and Producer. When being pulled into Levitate, we can recognize a connection to both users and not just one— but there will always be one contact owner. Read more about connection types + integrations here.
Q: Can Super Admins restrict which user roles are allowed to import contact lists?
A: Contact import access is an Editable account setting, meaning it can be configured to limit which roles may import contacts. By default, the ability to import contacts is available to users who have connected their email. If your organization needs to restrict contact imports to Super Admins only — or any other role configuration — reach out to your Success Specialist or our Support team to have the setting updated.
Q: Can Limited Users connect a Google Business Profile or create Satisfaction Surveys?
A: No. Connecting a Google Business Profile and creating Surveys and Events are both restricted to Admins and Super Admins — they are Hard-coded features that cannot be enabled for Limited Users or standard Users. See the permissions table above for the full breakdown of what each role can access.
Q: How does a newly invited user complete their account setup and log in?
A: When an Admin or Super Admin invites a new user, Levitate sends an invitation email to the address provided. The new user clicks the link in that email, creates their account, and connects their email — Levitate then takes them straight to their dashboard, ready to log in going forward. If the invitation email has not arrived, ask the invitee to check their spam folder, or have an Admin resend the invite from the Manage Users settings page.
Q: Why are some contacts skipped when a limited user sends an email or runs a bulk send?
A: Limited users can only send to contacts they personally own. Contacts owned by other users — including public contacts — are not accessible for sending from a limited user account, so those contacts are skipped during bulk sends. If your team needs a user to reach all shared contacts, upgrading them to a standard User role allows sending to public contacts. Upgrading to Admin additionally allows sending on behalf of other users and provides visibility into all scheduled content and key date cards across the account.
Q: What changes when a limited user is upgraded to admin, and are there any downsides?
A: Upgrading a limited user to Admin expands their access significantly. Admins can send to all public contacts (not just contacts they own), see contact owners and connections, view all scheduled content, manage key date cards for all contacts, create and manage automations, send and post on behalf of other users, and access additional account-level features like creating surveys and connecting a Google Business Profile. Because admins can act on behalf of other users and access broader contact and scheduling data, consider whether that level of access is appropriate before upgrading. If you only need the user to stop having contacts skipped in sends, a standard User role may be sufficient — it allows sending to public contacts without granting the full admin permission set.