Request access, invite colleagues and manage membership.
Reviewed · 2026-10-12
On this page · 6
1. Request membership
- Sign in → Grants → Join.
- Find a grant or project and submit a request. Grant and child-project memberships are separate.
- Check Notifications for approval. After joining a grant, you can also request a child project from the grant homepage.
- Reopen Grants → your project after approval. If unavailable, ask the manager to check both approval and active participation.
2. Invite a colleague as a manager
- Open the grant or project → Participants and invitations.
- For an existing member, choose the researcher under Add participant, review the role and management permission, then save.
- For a new member, generate an invitation link, copy it and send it yourself. The recipient follows the link, signs up or signs in, then accepts.
- Registration alone is not acceptance. Confirm the recipient in the participant list. Issue a new link if expired. The platform does not automatically email invitations.
3. Approve, change roles or remove participation
- Open a join-request notification, check its scope and applicant, then approve or reject.
- Use the participant list to assign or remove management permission. Grant managers manage that grant and its child projects; project managers manage their project.
- Removing participation ends access to that scope; it does not delete the account or remove unrelated memberships.
- If controls are missing, check your management role. Lab management is available to platform administrators.
Pending management requests
- Platform administrators can open the profile menu to see the awaiting-reply count next to Support. It counts unresolved new tickets and tickets whose latest reply came from the requester. An administrator reply clears that waiting state; a requester follow-up adds it again.
- The Review change requests card in Lab management counts pending metadata and deletion requests you currently have permission to review. Decided requests and inaccessible targets are excluded.
- Each Membership and invitations card counts pending membership approvals for that lab. Project/grant applications and unused invitation links are not added.
- Zero counts are hidden. Reopen the profile menu or management page to load current counts; returning to the page also refreshes them. These counts reflect pending work, separately from unread notifications.
Permanently delete a member account
- As a platform administrator, open Lab management → Members and invitations. Choose Permanently delete account on the member card. Suspension is reversible; permanent deletion is not.
- Review the username, email, all lab memberships, connections/calendar credentials/report schedules to stop, private AI conversation count and Lumen balance. This deletes the platform account across all labs, rather than removing only one lab membership.
- You cannot delete your own account here. Transfer the last active PI role first. Transfer owned grants/projects through Researchers → the successor's management page → scope → transfer responsibility. Settle any Timebank balance before deletion.
- Enter the target username exactly and your own administrator password. Check the irreversible-deletion acknowledgement, then submit. Review again if ten minutes elapse or the target changes. Cancel performs no deletion.
- The original login row, memberships, profile/personal settings, private AI conversation text and memory, favorites, follows, notifications and personal Zotero credentials are removed. Existing sessions lose access. Researcher references become inactive anonymous identities.
- Research reports, shared documents, comments and ledger history retain an anonymous, non-login author reference. Names and source text within research bodies/attachments are not rewritten. Connections created by the account lose credentials and stop collecting; report schedules stop. Another manager must reauthorize needed shared connections.
- This affects the current platform database. Previous operational backups and original accounts/material on GitHub, Google, Notion and other services are not deleted by this button. Review the complete impact before submitting.
Check join and change-request notifications
- Open join or metadata-change requests from Notifications and check the scope and applicant.
- Review and approve or reject with the required current authority. An administrator label alone does not replace a scope-specific authorization check.
- If no alert appears, check relevant notification categories, administrator policy and approval rights. Reading or deleting a notification does not itself decide the request.