Team access

If you have team members or collaborators who need access to your rasa.io account, you can invite them and control what they can do. This article covers how.

Where to manage your team

Go to Settings → Team & Permissions. You'll see a Team Members table showing everyone with access, their role, status, and which newsletters they can edit.

Inviting a new team member

1. Click + Invite User at the top right
2. Fill in their First Name, Last Name, and Email Address
3. Choose a Role:

• Admin — can do everything, including managing the team
• Member — can edit messages they have access to, but cannot add/remove or change other users

1. Set Newsletter Access — check the newsletters, sequences, and blasts this user should be able to work with. You can scope to one, several, or all.
2. Click Send Invitation

They'll get an email with a link to set up their account.

Roles explained

Admin:

• Manage the team (invite, edit, disable, delete users)
• Edit all account-level settings
• Everything a Member can do

Member:

• Edit content, sources, layouts, and scheduling for the messages they have access to
• Manage contacts and lists
• Cannot manage other team members or change team-wide settings

For most organizations, you'll have a small number of Admins (1-3) and the rest as Members.

Newsletter access

When inviting (or editing) a user, you control which messages they can edit:

• Just one newsletter — useful when team members manage specific brands or products
• Several newsletters — for senior editors or shared roles
• All newsletters, sequences, and blasts — for marketing leads and admins

You can also grant access to specific sequences or blasts.

Editing or removing a user

In the Team Members table, each user has actions:

• Edit — change their name, role, or newsletter access
• Enable (for inactive users) — re-activate someone who was disabled
• Disable — remove their access without deleting their record (preserves history)
• Delete — fully remove the user
• Resend Invite (for pending users) — re-send the invitation email
• Delete Invite (for pending users) — cancel a pending invitation

Statuses

• Active — currently has access
• Pending — invited but hasn't accepted yet
• Inactive — was active, has been disabled (re-enable anytime)

Best practices

• Limit Admins — only people who need to manage the team should be Admins
• Use Members for editors — most people only need editorial access, not team management
• Disable instead of delete when someone leaves temporarily — easier to re-enable than re-invite
• Audit periodically — quarterly, review who has access and whether they still need it
• Use specific newsletter access when possible — don't grant "all newsletters" to someone who only manages one

Security recommendations

• Encourage everyone to enable two-factor authentication on their profile
• Use unique passwords (no sharing)
• Remove access when team members leave
• Use specific newsletter access rather than "all" when team members only need a subset

Common questions

Can a Member become an Admin later?

Yes. Edit the user and change the role.

What happens to content created by a deleted user?

The content stays. Only the user's access is removed.

Can two Admins work on the same newsletter simultaneously?

Yes, though best practice is to coordinate to avoid stepping on each other's work.

Can I scope a Member to only see their newsletter's analytics?

Yes — their newsletter access controls what they can see and edit.

What's next

• Setting up your account — initial team setup
• Settings overview — other account configuration