Skip to main content

Creating a new organization

When a new fraternity or sorority signs up, you provision their tenant. This is platform-admin work — it's how a new customer goes from contract signed to first sign-in.

Open the platform admin dashboard​

Sign in as a platform admin. You'll land at /platform/dashboard.

In the sidebar: Organizations.

The platform organizations list. The platform organizations list.

Create the organization​

  1. Click New organization.
  2. Set:
    • Name (e.g., "Phi Beta Kappa")
    • Type (Fraternity, Sorority, Co-ed, Other)
    • Slug — auto-generated from name; used in URLs (apply.greekmanage.com/[slug])
    • Initial state — Active or Inactive
  3. Click Create.

GreekManage automatically:

  • Creates the org record
  • Generates 9 module records (all disabled by default)
  • Provisions an isolated database schema (per-org row-level security)
  • Creates the public apply route (disabled until configured)

Add the first org admin​

After creating the org, the screen prompts you to add the first org admin.

  1. Search for the user (must already exist as a GreekManage user) or create new.
  2. Set their title.
  3. Click Send invitation.

The org admin gets a welcome email. From here, they take over — adding more admins, creating chapters, configuring modules, etc.

Module licensing​

Decide which modules are licensed to this org based on their contract:

  1. Open the org → Modules.
  2. Toggle each licensed module on.
  3. Set any module-specific limits (e.g., AI Services may have a per-month query cap).
  4. Save.

Org admins can enable/disable modules within their licensed set. They cannot enable modules outside their license.

Storage assignment​

By default, new orgs use the platform default storage. If the contract specifies a dedicated storage provider (e.g., they want their own S3 bucket):

  1. Open Modules → Storage in the org settings.
  2. The org admin configures it from there. → Storage configuration

For migration use cases (existing data being moved), coordinate with the customer's IT lead before the org goes live.

Brand setup​

Most platform admins handle the initial logo upload and primary color in collaboration with the customer:

  1. Open the org → Branding.
  2. Upload their logo.
  3. Set their primary color.
  4. Save.

→ Branding

Email config​

Confirm that platform-level email is configured before the new org gets sign-up flows. If email isn't set up, members won't get invitation emails.

→ Email config

Test the apply page​

If the org will use PNM intake:

  1. Have the org admin enable the Operations module.
  2. Configure the apply page.
  3. Submit a test application end-to-end.
  4. Verify the application reaches the chapter approval queue.

Hand off to the org admin​

A clean handoff:

  • Email the org admin with their welcome
  • Schedule a 30-minute training session
  • Walk them through: chapters, regions, dues, modules, branding
  • Point them to the org admin section of these docs

Suspending an organization​

If a contract ends or there's a billing issue:

  1. Open the org → Status → Suspended.
  2. Add a reason for the audit log.
  3. Save.

Suspended orgs:

  • Block sign-ins
  • Show a banner with your reason on attempted sign-in
  • Preserve all data
  • Stop generating invoices / charges
  • Block API access

Reactivate by setting status back to Active.

Tips​

  • Never delete an org. Even after contract end, suspend instead. Deletion is permanent and customers always come back asking for data.
  • Document the customer's setup choices. Keep notes on storage choices, modules, branding — useful for support and renewals.
  • Test the apply page yourself before turning the org loose. Catch misconfigurations early.