NoCodeBackendHelp Center
Build and manage

User Invitations & Granular Quota Delegation

How to invite team members and clients with isolated accounts, allocate database and AI quotas, and manage seat limits.

Account owners, team leads, and agency managers6 min read

User Invitations & Granular Quota Delegation

NoCodeBackend allows account owners to invite team members, developers, and clients into the platform with dedicated, isolated accounts while delegating specific portions of their plan quotas—including databases, AI generation credits, webhooks, pre-hooks, daily snapshots, and Cloudflare R2 storage.

1. Overview: How Invitations Work

Unlike traditional tools that force all team members into a single shared workspace where everyone sees and edits the same database, NoCodeBackend uses an Isolated Account Architecture:

  • Independent, Isolated Accounts: Each invitee receives their own private account with their own credentials. They do not share your dashboard view, secret keys, or database schemas.
  • Dedicated Quota Delegation: As the account owner, you act as the quota pool manager. You decide exactly how many databases, AI credits, pre-hooks, webhooks, and snapshots each invitee can create from your subscription pool.
  • Client & Team Privacy: Invitees cannot see other invitees, cannot view your personal databases, and cannot exceed the limits you assign to them.

2. Seat Capacity by Plan

The number of invitee seats available to you depends on your active subscription or lifetime tier:

| Plan / Tier | Included Invitee Seats | Quota Delegation Model | | :--- | :--- | :--- | | Starter Plan | 5 Seats | Pool delegation from owner limits | | Professional Plan | 25 Seats | Pool delegation from owner limits | | AppSumo Tier 3 | 3 Seats | Pool delegation from owner limits | | AppSumo Tier 4 | 10 Seats | Pool delegation from owner limits | | AppSumo Tier 5 | 20 Seats | Pool delegation from owner limits |

đź’ˇ

Note: If your plan does not include invitation seats (e.g. Free plan or lower tiers), you can upgrade your plan under Billing to unlock user invitations.

3. Delegable Resources & Granular Limits

When you invite a user, you specify the exact quotas they are granted:

  1. Databases (Mandatory, Min: 1):
    • Every invitee must be allocated at least 1 database to use the platform.
    • The allocated count is deducted from your owner database capacity and assigned to the invitee.
  2. AI Generation Credits:
    • Allocate AI credits for natural language schema generation.
    • Set to 0 or disable AI to prevent the invitee from consuming your AI credits.
  3. Outbound Webhooks:
    • Grant a specific number of outbound webhook endpoints the invitee can create across their databases.
  4. Pre-Hooks (Server-Side Middleware):
    • Grant a specific number of Pre-Hook interceptors for data validation and calculations.
  5. Daily Database Snapshots:
    • Allocate daily automated or manual snapshot backup capacity.
  6. Cloudflare R2 File Storage:
    • Toggle whether the invitee is permitted to connect and configure Cloudflare R2 object storage.

4. Step-by-Step Guide: Inviting a User

Step 4.1: Access the Invites Dashboard

  1. Log in to your NoCodeBackend dashboard.
  2. In the top navigation bar or sidebar, click Invites (or navigate to /invites).
  3. You will see your Owner Quota Overview cards showing:
    • Seats Used / Available: e.g., 1 of 10 seats used.
    • Databases: Total plan capacity, databases you created, databases allocated to invitees, and remaining unallocated databases.
    • AI Credits, Webhooks, Pre-Hooks, Snapshots: Real-time breakdown of pool availability.

Step 4.2: Fill Out the Invitation Form

  1. Click + Invite New User.
  2. Enter the recipient's Email Address.
  3. Specify their Database Limit (minimum 1, up to your remaining available databases).
  4. Specify limits for AI Credits, Webhooks, Pre-Hooks, and Daily Snapshots.
  5. Toggle Allow R2 Storage to Yes or No.
  6. Click Send Invitation.

Step 4.3: Invitee Acceptance

  • The invitee receives an email with an activation link.
  • Their status in your dashboard will display as Pending invitation until they complete signup.
  • Once they register and sign in, their status transitions to Active.
  • Their dashboard is provisioned immediately with the exact resource limits you specified.

5. Modifying Invitee Limits & Quota Recouping

You can adjust an invitee's resource allocation at any time by clicking the Edit (Pencil) button on their invitee card.

Safe Recouping & Minimum Consumption Rules

To protect system integrity and prevent breaking active databases, NoCodeBackend strictly enforces:

  • Strict Minimum Consumption Check: You cannot reduce an invitee's limit below the number of resources they have already created or used.
    • Example: If an invitee was given 10 databases and has already created 4, you can reduce their limit to 4, 5, or 6, but not to 3 or 2.
  • Instant Owner Recouping: When you decrease an invitee's limit (e.g. from 10 down to 4), the unallocated difference (6 databases) is instantly returned to your owner pool for you to use or reassign to other team members.

6. Deleting Invitees & Complete Data Purge

When an invitee leaves your organization, completes a client project, or is removed by you:

  1. Click the Delete (Trash) button on their invitee card.
  2. Confirm the deletion prompt.
  3. What happens during deletion:
    • Complete Permanent Purge: The invitee's account profile, access credentials, and all databases they created (including tables, records, schemas, and API keys) are permanently deleted from the system.
    • Full Quota Recouping: All quotas previously allocated to that invitee (all databases, AI credits, webhooks, pre-hooks, and snapshots) are 100% recouped back to your owner quota pool immediately.
    • Seat Released: The invitation seat is instantly freed up, allowing you to invite a new team member.

7. Best Practices & Security

  • Principle of Least Privilege: Allocate only the databases and AI credits the invitee needs for their current project. You can always increase their quota later.
  • Client Hand-Offs: When building backends for clients, use invitations to let them build inside their own isolated sandbox. When the engagement ends, they can either transfer databases or you can revoke access.
  • No Shared Keys: Invitees generate their own Secret Keys and MCP tokens. They can never see your account's Secret Keys, Stripe credentials, or billing settings.

8. Troubleshooting

Common Errors

Error: Cannot reduce database limit below X

  • Cause: The invitee has already created X active databases. Lowering their limit below X would leave orphaned databases.
  • Resolution: If you need those databases back, have the invitee delete their unused databases, or delete the invitee entirely to recoup all capacity.

Error: You have exhausted your available databases

  • Cause: Your remaining unallocated databases pool is 0.
  • Resolution: Either edit existing invitees to reduce their unused limits, delete inactive invitees, or upgrade your plan to increase your total database pool.

Error: Invitee did not receive the invitation email

  • Cause: Email was caught in a spam/junk filter, or the recipient email had a typo.
  • Resolution: Check the spam folder for an email from NoCodeBackend. You can also delete the pending invitation and re-send it to the verified email address.
User Invitations & Granular Quota Delegation | Help Center