Admin Guide

Admin guide to configuring, activating, and maintaining institutional packages for partner organizations.

Creating & Managing Institutional Packages

Institutional Packages let you grant a specific plan tier (Basic, Pro, or Premium) to an entire organization's members. This guide covers everything you need to configure and maintain a package.

Access: Admin-only. Navigate to Edit Home Page → Institutional Packages (or the admin sidebar entry) to manage packages.

Creating a New Package

From the Institutional Packages manager, click New Package and fill in the following fields:

| Field | Purpose | |---|---| | Organization Name | Display name of the institution (required). | | Granted Plan | The plan tier all members receive: Free, Basic, Pro, or Premium. Defaults to Premium. | | User Limit | Maximum number of members. 0 means unlimited. | | Email Domain | The organization's email domain, used for automatic matching at signup (e.g. university.edu). Lowercased, no @. Leave empty for invite-code-only orgs. | | Invite Code | Optional code members can enter at signup. Must be unique across active packages. Auto-generated if left empty. | | Contact Email | Optional billing/admin contact for the institution. | | Description | Internal notes about this package (billing cycle, contract terms, etc.). | | Active | Toggle. Inactive packages stop accepting new members; existing members keep access until removed. |

Choosing an Onboarding Method

There are two ways members can join a package. You can use either or both:

1. Domain Matching (Automatic) Enter the organization's email domain in the Email Domain field. Any user who signs up with an email at that domain is automatically linked to the package — no code needed. This is ideal for universities and companies with a shared email domain.

2. Invite Codes (Manual) Leave the domain blank and distribute the generated invite code to members. They enter it on the Sign Up page. This suits guest users, contractors, or organizations without a shared domain.

You can combine both: set a domain and an invite code, so members join automatically via email or manually via the code.

Editing a Package

Select any package to update its fields. Common reasons to edit:

• Upgrade/downgrade the granted plan.
• Adjust the user limit (note: lowering the limit does not remove existing members, but blocks new ones).
• Change the invite code if it has been shared outside the organization.
• Update the contact email or internal description.

Changes to the granted plan apply to all current members on their next sign-in.

Activating & Deactivating

Use the Active toggle to control whether a package accepts new members:

• Active (default): New sign-ups via domain or invite code are accepted.
• Inactive: New sign-ups are rejected. Existing members keep their access until you manually remove them or the package is reactivated.

Deactivate a package when a contract is paused or under review — you won't lose existing members, but you'll prevent anyone new from joining.

Removing Members

To remove a specific member from a package, edit their UserProfile and clear the institutional_package_id field. Their plan will revert to Free on their next sign-in.

Removed members can rejoin if the package is still active and they still match the domain or have the invite code. To permanently block rejoining, deactivate the package or change the invite code.

Best Practices

• Use clear, memorable invite codes — members will mistype complex codes.
• Set a user limit on paid packages to prevent unexpected overages.
• Store the contract/billing contact in the Contact Email and Description fields for quick reference.
• Rotate invite codes if they leak outside the organization.
• Deactivate, don't delete packages when a contract ends but you may need to reference the record later.