--- title: "Invitations" description: "How invitations work, how to accept one, and what happens if it expires." --- Invitations are the only way to join an existing org (you can't request access from the outside). An owner or admin sends one; the recipient clicks the link in the email and Google-signs-in. ## Sending an invitation Covered in detail in [Invite your team](/docs/workflows/invite-team/) — from the sender's side, it's three fields and a button. ## Accepting an invitation 1. **Open the email.** The subject is `You've been invited to on simple-plm`. The body has a single accept button. 2. **Click the button.** This opens `https://simple-plm.com/invitations/` in your browser. 3. **Sign in with Google** if you're not already signed in. The Google account you choose **must** match the email on the invitation — simple-plm rejects mismatched accounts to prevent accidental cross-account binding. 4. **You're in.** The dashboard loads in the invited org with your assigned role. If you're already a member of other orgs, the invited org is added to your org list; you can switch between them from the top-left. ## Expiry Invitations expire after **7 days**. After that, the link returns "Invitation expired" and the token is invalidated. Ask the sender to issue a fresh one — there is no self-service renew. ## Revoking The sender (owner or admin) can revoke a pending invitation any time from Settings → Team → **Pending invitations**. Revocation is instant; if the recipient hasn't clicked the link yet, the token returns "Invitation revoked" when they do. Already-accepted invitations cannot be revoked — to remove someone after they've joined, change their role to none or remove them from the **Active members** list. ## One invitation per address simple-plm collapses duplicate invitations: if you invite `alice@example.com` and an admin invites her again before she accepts, the second invitation supersedes the first and the original token is invalidated. This keeps Alice from seeing two emails and clicking the wrong one.