Project settings and collaborators
Invite InAppify project collaborators, accept email invitations, choose roles, customize permissions, resend invitations, and remove members safely.
Collaborators use their own accounts to work on your project, without sharing the owner's password or secret key. Membership is limited to that project and the member's permissions; it does not grant access to every project or transfer ownership.
Basic project settings
Select the project and open Project settings → Settings. Update the project name and save. The project identifier is not a secret API key or SDK key. Project deletion is sensitive and must not be used to rotate keys or troubleshoot an integration.
Other tabs lead to activity history, reporting, payment gateways, and custom domains.
Before inviting
- Create a project and select it.
- Obtain the email address the collaborator will use to sign in.
- Identify the minimum permissions needed for their work.
- Be the owner or a member allowed to invite others. Only the owner can invite a Manager.
If capability or capacity restrictions block invitations, check feature capacity and your current account status. This guide does not define a universal collaborator limit.
Invite from the dashboard
- Sign in to the dashboard and select the project.
- Open Project settings → Collaborators.
- Select Invite collaborator.
- Enter the email and choose a role.
- Send the invitation. The member appears as Pending, and an invitation email is sent.
- Ask them to accept using the account associated with that email.
Sending an invitation does not activate access; acceptance does. If the email already appears in the project's member list, check the existing invitation rather than creating a duplicate.
Choose a role
| Role | Base permissions and purpose |
|---|---|
| Owner | Original project owner; invitations do not transfer ownership. Not selectable in the invite form. |
| Manager | Broad project and team management for a trusted person. Not equivalent to ownership and cannot customize member permissions. |
| Developer | Project settings, apps, keys, and technical areas such as catalog, offerings, and payment links; no base financial permissions. |
| Support | Customer and access viewing, customer access grants and checks, and some operational information; no base financial or most app-setting permissions. |
| Viewer | Read permitted areas without editing; some financial details, keys, and sensitive settings are excluded. |
A role provides default permissions. The owner can customize a member's permissions, so effective access may differ. Support is not strictly read-only: its base permissions include granting customer access.
Use Viewer for permitted report inspection and Developer for SDK and app configuration. Do not grant Manager to everyone merely to solve an isolated permission error.
Accept an invitation
- Open the invitation email and follow its link.
- Sign in using the invited email, or register with that address.
- Verify your account email; an unverified email cannot accept.
- Return to the invitation and select the start-collaboration action.
- The project becomes accessible and the invitation status changes to Accepted.
If the browser is signed into another account, sign out first. Possession of the invitation link is insufficient: the signed-in account email must match. Do not publish invitation links.
Resend an invitation
For a pending member, choose Resend from the row's actions. A new link is issued and the old link becomes invalid; use the latest email.
Invitations can expire. Resend an expired invitation; opening an old email does not refresh it. Accepted invitations cannot be resent.
Change roles and customize permissions
Use the member row's role selector. Only the owner can manage the Manager role or change or remove a Manager; other members also need the relevant team-operation permission.
Changing a role clears previous custom permission overrides and applies the new role's defaults. Review custom access again after a role change.
For finer control, the owner opens Manage permissions, enables or disables operations in the relevant groups, and saves. Viewing, creating, editing, and deleting are separate permissions; enabling one does not authorize every operation in that area.
These permissions control a member's dashboard account, not secret API key abilities. Consider the security consequences of allowing members to create server keys.
Remove a collaborator
Select and confirm removal from the member's actions. That membership loses project access; the person's account, project, and customer purchases are not deleted. The owner cannot be removed from this list.
Removal does not automatically revoke secret keys previously created or copied. Review API keys and other credentials the person held, and revoke or rotate them where needed. To add a removed member again, send a new invitation requiring fresh acceptance.
Troubleshooting
- No invite button: check the selected project and your invitation permission.
- Manager invitation denied: the owner must perform it.
- No invitation email: check the address and spam folder, then resend if needed.
- Invalid or expired link: use the latest invitation; old, accepted, or removed-membership links cannot be used.
- Account cannot accept: sign in with the invited address and verify its email.
- Project missing: check invitation acceptance and membership, then refresh the project list.
- Missing dashboard section: check the role and that section's permissions; restricted access may be intentional.
After acceptance, check using the collaborator's account that required areas are accessible and unnecessary operations remain restricted. A name in the member list alone does not verify correct access.