ScaffoldHub
  • Introduction
  • Modeling
  • Setup
    • NextJS
    • File Storage
    • Payments with Stripe
  • Debugging
  • End-to-end and Unit Tests
  • Deployment
    • Deploy to Vercel
  • Features
    • Projects
    • Preview
    • Tenants
    • Subscriptions and Payments
    • Security
    • File Storage
    • Authentication
      • Sign-in and Sign-up and Social Sign-in
      • Invitation
      • Password Reset
      • Password Change
      • Email Verification
    • Entity
      • Form
      • Filter and List
      • Export
      • Import
    • Audit Logs
    • Internationalization (I18n)
    • API Keys
    • API Documentation
  • Package.json
  • Support
  • Changelog
    • Documentation
    • Scaffolds
  • Custom Development
  • Legacy Scaffolds
  • Go to ScaffoldHub
Powered by GitBook
On this page
  • Single-tenant
  • Multi-tenant
  • Sign-up
  • Managing workspaces
  1. Features

Tenants

PreviousPreviewNextSubscriptions and Payments

Last updated 1 year ago

ScaffoldHub projects allow you to scope the application's data in two different ways.

Single-tenant

The single-tenant mode scopes the application data to a single tenant.

Every entity (for example, customer, product, or order) that you create will be available to all users of the platform to access, restricting only their to access it.

By default, when you register the first user, they will be set as the application's admin.

Multi-tenant

The multi-tenant mode allows you to create multiple workspaces.

Sign-up

After a new user signs up, they are asked to create a new workspace.

Managing workspaces

The workspace term is just a label; you can to anything appropriate to your business model. Examples are Organizations, Companies, Teams, etc.

Each workspace has its , , Settings, and .

If the user has been but didn't come from the invitation email, they will be asked if they want to accept the invitation or create a new workspace.

Users can switch, create, edit, or delete workspaces on the Workspaces page, accessed via the User's menu. Permission to edit and delete a specific workspace depends on the the user has in that workspace.

rename it
Users
Audit Logs
Entities
invited
role
roles and permissions