Invitations

Send invitations with the role and the apps already set, track the ones still pending and revoke the rest.

Who can use this? Workspace owners and admins.

Decide what role each person lands with and which apps they open before they ever arrive. Nest gathers here every pending invitation in the workspace, not just yours.

The table

Check at a glance who is invited, what role they land with and when their link expires.

Column What it shows
Email The person invited.
Role The role they will have on accepting.
Apps One chip per granted app. If you ticked none it says "None".
Expires The deadline; expired rows carry an "Expired" badge.

Hover a chip to see the standing for that app: Member or Admin.

One pending-invitation row: the address, the role, the apps granted, the expiry date and the revoke button.

Sending an invitation

Invite somebody with three things: the address, the role and the apps. Choose the apps one at a time, with three options each: no access, Member or Admin, for each of Wrap, Flow, Swarm and Zap.

The person arrives with that in place from minute one, and nobody has to come back and adjust their access.

If you give them workspace Owner or Admin, Nest pins every row to Admin: that role already grants every app.

If the address already has an Eel account, Nest sends no invitation: it adds the person to the workspace directly and tells you so.

If the email does not go out, the invitation still exists. Copy the link in the dialog and share it yourself.

Revoking

Click Revoke on the invitation's row and confirm. The link sitting in the person's inbox stops working immediately.

What the recipient sees

The person gets a link that opens auth.eel.software. With no account they create one right there; with an account they just accept. Either way they end up inside the workspace with the role and the apps you chose.