Tenant settings
What a Customer's admin changes inside their own Tenant, what the Startup sets for everyone, and what no one below may loosen.
A Setting is a choice a Tenant inherits from its nearest holder unless it sets its own. Studio, then Startup, then Tenant: the nearest value wins, and a locked one wins everywhere below it.
Who sets what
| Set by | For | Leaseline's example |
|---|---|---|
| The founder or the Startup's agents | Every Customer | Notices go out 60 days before a lease ends |
The Customer's owner or admin | Their own Tenant | Riverside Property sends its notices at 90 days |
A child may tighten a value but never loosen it. Leaseline locks "notices go out at least 30 days ahead", so Riverside Property may choose 90 and may not choose 14.
The settings screen
Every saas App compiles one settings screen per Tenant. It lists each Setting the Tenant may change, its inherited value, and who set it. A locked Setting shows its value and its holder, with no control.
Members, notices, connected tools and billing sit beside it, each on its own screen:
Every change is an Action
Changing a Setting is a call like any other. It leaves an Action with who changed it and the value before, so the audit log shows who moved the notices to 90 days.
Next
Notices covers how each person chooses to hear from the App.