Skip to main content
GoDizzy is built for teams. Once you invite someone to your organization, they have access to all shared routing configs — staging and production environments, all collections, and all rules within those environments. Everyone can view, edit, and save changes.

​
Invite a teammate

1

Open the Team page

In the dashboard, navigate to Team. You will see a list of current organization members and any pending invitations.
2

Enter email addresses

In the Invite members section, enter one or more email addresses. You can separate multiple addresses with commas or new lines.
3

Send the invitations

Click Send invites. GoDizzy sends an invitation email to each address.
  • If an address is already a member of your organization, you will see a notice instead of a duplicate invite being sent.
  • If an address already has a pending invitation, GoDizzy will offer to resend it rather than create a duplicate.
  • Invalid email formats are flagged inline before sending.
4

Invitee accepts and joins

The invitee receives an email with an acceptance link. When they click it:
  • New users complete sign-up and then join your organization.
  • Existing GoDizzy users sign in and are added to your organization automatically.
After acceptance, the new member appears in your Members list and has immediate access to your shared environments.

​
Manage pending invitations

From the Team page you can see every invitation that has been sent but not yet accepted, along with who sent it and when.
  • Resend — If a teammate did not receive the email, click Resend on their pending invitation.
  • Revoke — If an invitation was sent in error, click Revoke. The invitation link is immediately invalidated.
Any organization member can resend or revoke invitations — there are no separate admin roles.

​
Seat limits

The number of teammates you can have in your organization depends on your plan:
PlanSeats
Free1
Starter3
Pro10
Business30
When you reach your plan’s seat limit, you will need to upgrade before sending additional invitations. See the pricing page for details on each plan.
Seat limits apply to active organization members, not pending invitations. Revoking a pending invite or removing a member frees up a seat.

​
Access model

All organization members have equal access to shared environments. There are no roles or permission tiers — if a teammate is a member of your organization, they can do everything you can do in staging and production.
Development environments are private. Each team member has their own personal development environment that only they can see. You cannot view, edit, or access a teammate’s development environment, and they cannot access yours. This isolation lets everyone experiment freely without risk of interfering with each other’s work.Staging and production environments are visible and fully editable by all organization members.

​
Collaboration patterns

All teammates can edit the staging environment directly. If two people edit the same rule at the same time, the last save wins. Use the rule’s version history to see who changed what and revert if needed — every save records the author’s email address.
Ask your teammate to build their config in their development environment and copy it to staging when ready. You can then inspect the staging collection, test it against your agent or integration suite, and copy it to production when satisfied — all without touching their development environment.
If a teammate’s change to a production rule causes an issue, open the rule’s version history in the production environment. You will see every version with the editor’s email and timestamp. Revert to a prior version — GoDizzy creates a new version with the old content, preserving the full audit trail.