Invite teammates and assign roles
Last reviewed
For: An Organization admin setting up their team.
You’ll accomplish: understanding the two roles and what each can do, inviting people to the right one, removing access when someone leaves, and handing off ownership safely.
PropSocket keeps roles simple on purpose: there are two. An admin runs the account; a member does day-to-day work. This article shows what each can do and how to manage people.
You don’t need to write any code for any of this.
1. The two roles, side by side
| What they can do | admin | member |
|---|---|---|
| Invite teammates | Yes | No |
| Change another teammate’s role | Yes | No |
| Remove teammates | Yes | No |
| Connect or disconnect a PMS integration | Yes | Yes |
| Pause, resume, or delete an integration | Yes | Yes |
Create live (ps_live_) API keys |
Yes | Yes |
Create test (ps_test_) API keys |
Yes | Yes |
| Revoke API keys | Any key | Any key |
| Configure webhooks | Yes | Yes |
| View sync history, webhook logs, and your synced data | Yes | Yes |
| Edit Organization name, billing, and sign-in settings | Yes | No |
| View billing and invoices | Yes | No |
The short version: the line between the two roles is the Organization Settings page. Admins are the only ones who can manage people, billing, the Organization name, and sign-in settings. Members can do everything else — connect, pause, and delete integrations, create live and test API keys, configure webhooks, and read all your data. In other words, a member can do nearly all the day-to-day work; the role exists mainly to keep billing and team management in admin hands.
A note on limiting an engineer’s access: Because members have broad reach (including deleting integrations and creating live keys), the role isn’t a way to sandbox someone. If you need to give an engineer genuinely limited access, hand them a read-only API key rather than relying on the member role (see Generate and rotate API keys). That scopes exactly what their integration can touch.
2. Invite a teammate
Only admins can invite. PropSocket sends the invitation through its secure sign-in provider (WorkOS), so the invitee gets a clean, verified sign-in link.
- Open Settings → Team Members (the Settings link in the sidebar — it’s visible only to admins).
- Enter the teammate’s work email.
- Choose their role: admin or member. When in doubt, pick member — you can promote them later.
- Send the invite.
The invitee gets an email, clicks to accept, and sets up their sign-in the same way you did. If your company uses single sign-on (SSO), they’ll sign in through that. See Your first 30 minutes in PropSocket for what their first-time experience looks like.
If an invite link expires before they accept, just send a new one.
3. Change someone’s role
People’s responsibilities change. To promote a member to admin (or step an admin down to member):
- Open Settings → Team Members.
- Find the person and pick a new role from the dropdown next to their name. (You can’t change your own role — ask another admin if you need yours changed.)
The change takes effect right away the next time they act in the dashboard. Keep at least one admin at all times — don’t step the last admin down (more on that below).
4. Remove someone’s access
When a teammate leaves the company or no longer needs PropSocket, remove them promptly. Removing a person:
- Ends their access to your Organization immediately.
- Does not delete any integrations, data, or webhooks they set up — those belong to the Organization, not the person.
To remove someone, open Settings → Team Members, find them, and click Remove next to their name. You’ll be asked to confirm. (You can’t remove yourself — ask another admin.)
Don’t forget the keys. Removing a person from the Organization does not automatically revoke API keys they created. If they had access to any keys — especially production
ps_live_keys — rotate or revoke those as part of offboarding. See Generate and rotate API keys.
5. Transfer ownership
There’s no single “owner” title in PropSocket — the admin role is what carries account control. To hand the account to someone else:
- Make the new person an admin (invite them as admin, or promote an existing member — step 3).
- Confirm they can do admin things — see billing, manage people, manage integrations.
- Step the previous admin down to member, or remove them if they’re leaving.
Always make the new admin before removing the old one, so the Organization is never left without an admin. (As a safeguard, you can’t remove yourself or change your own role — so the last admin can never accidentally lock the Organization out from the dashboard.) If you ever do end up with no admin (for example, the only admin left the company without handing off), contact support — we can help restore admin access.
If this didn’t work
If an invite won’t send or accept, a role change doesn’t seem to apply, or you’ve lost admin access entirely, we’ll help.
Open a support ticket by emailing support@propsocket.io and include:
- Organization slug (the short name in your dashboard URL, e.g.
acme-residential) - The teammate’s work email (the one on the invite)
- The role you intended for them
- What you expected vs. what you saw
- A screenshot of the team management area
Please do not include passwords or sign-in codes in a ticket — our team will never ask for them.
Didn't solve it?Talk to us — a real engineer replies within one business day. Or browse therest of the help center.