Invite Collaborators to an Organization

This recipe adds team members to an existing Organization. You choose a role, select scopes, and send the invite. It also covers what the invitee experiences.

Prerequisites

• WordPress admin access, or portal access as the Organization's owner or admin.
• The Organization already exists and is verified. See Onboard an Organization if needed.
• You know the email address of each person you want to invite.

Steps

Sending the invite

Step 1. Go to MIDDAG Account > Organizations and open the target Organization. Navigate to the Team tab.

Alternatively, if you are an Organization owner or admin working in the portal, go to Team > Invite Member.

Step 2. Click Add Collaborator.

Step 3. Enter the invitee's email address.

Step 4. Select a role:

Role	What they can do
admin	Full access to all scopes. Can invite and remove members.
member	Access only to assigned scopes. Cannot manage team.
guest	Read-only access to assigned scopes. Cannot manage team.

The owner role cannot be assigned during invite. There is exactly one owner per Organization, set during onboarding. Ownership can be transferred later.

Step 5. Select scopes that determine what the collaborator can see and do:

Scope	Grants access to	Typical role
organization	Organization profile, team list	Everyone
finances	Invoices, tax invoices	Finance team
orders	Order history	Purchasing
licenses	License management, site activation	IT/DevOps
tickets	Service requests	Support contacts
quotes	View and accept quotes	Purchasing/Managers
contracts	Contract viewing, SLA terms	Legal/Management
documents	Shared document library	Varies
downloads	Product downloads	IT/DevOps

You can select individual scopes or use a template (e.g., "Finance" assigns finances + orders + quotes automatically).

Step 6. Click Send Invite.

Step 7. The system creates a collaborator record with status pending and sends an invitation email containing a unique token link.

Bulk invites

Step 8. To invite multiple people at once, click Bulk Invite. Enter a comma-separated list of emails. All invitees receive the same role and scopes.

What the invitee experiences

Step 9. The invitee receives an email with a link (valid for 7 days).

Step 10. They click the link. If they already have an account, the system links them to the Organization. If they are new, the registration form asks them to set a password.

Step 11. After completing registration, they can log in to the portal. They see only the sections permitted by their assigned scopes.

After the invite

Step 12. Back on the Team tab, verify the collaborator status changed from pending to their assigned role (e.g., member).

Step 13. To change scopes or role later, click the collaborator's name on the Team tab, adjust settings, and click Save. Changes take effect immediately.

Step 14. To re-send an expired invite, find the collaborator with status pending, click Resend Invite, and a new token is generated.

Expected result

• The invited collaborator received an email and can access the portal after setting a password.
• Their portal view is limited to the scopes you assigned -- they see nothing outside those areas.
• The collaborator appears on the Organization's Team tab with the correct role and scopes.

Further reading

• Collaborator Management -- the conceptual flow behind team access.
• Collaborators -- role hierarchy and scope definitions.