Difference between revisions of "Features/Multi tenancy"
Jump to navigation
Jump to search
(Created page with "== Usages == TS has built multitennacy support allowing to build seggregated applications for multiple parties, while still having users working across organizational units. Data in the system can be handled in different ways * Owned by a single group of users * Shared ressource across groups (often readonly) * Hidden ressource (templates etc.) == SAAS onboarding == In TS it is quite easy to build SAAS application, becaue the onboarding can be fully automated. The pro...") |
(→Usages) |
||
| Line 6: | Line 6: | ||
* Shared ressource across groups (often readonly) | * Shared ressource across groups (often readonly) | ||
* Hidden ressource (templates etc.) | * Hidden ressource (templates etc.) | ||
Essentialy this feature is just one of the ways [[Features/Advanced_permissions|Advanced_permissions]] can be configured. | |||
== SAAS onboarding == | == SAAS onboarding == | ||
Latest revision as of 13:04, 10 November 2024
Usages
TS has built multitennacy support allowing to build seggregated applications for multiple parties, while still having users working across organizational units.
Data in the system can be handled in different ways
- Owned by a single group of users
- Shared ressource across groups (often readonly)
- Hidden ressource (templates etc.)
Essentialy this feature is just one of the ways Advanced_permissions can be configured.
SAAS onboarding
In TS it is quite easy to build SAAS application, becaue the onboarding can be fully automated.
The process includes
- User signup form
- Optionally accept from administrators
- Optional: Contract
- Generate and send contract
- Digital signing of contract
- Profile creation
- User and group creation
- Welcome information
Context switching
Users not belonging to a tenant group will sometimes need to impersonate one.
By clicking the context swtcher component, the system start to behaving as if that user was a tenant of that group.