Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixing incorrect reference to entities being cross-tenant #3274

Merged
merged 1 commit into from
Sep 16, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -752,7 +752,7 @@ Here's a table with the strengths and challenges of each option.
| [Tenants](#tenants) | True separation of users, API keys, connectors and other user related configuration | Cross-tenant user access, users can't be moved between tenants without resetting password |
| [Applications and Registrations](#applications-and-registrations) | Inherits settings from containing tenant, can separate users based on registration, with paid plan can configure application specific themes, unlimited roles| If FusionAuth SSO enabled user can SSO between each application, must check tokens in application |
| [Groups](#groups) | Contained in a tenant, can apply application roles to all members | Can't apply registrations to all members of a group, need lambda API call to add membership to tokens |
| [Entities And Grants](#entities-and-grants) | Fine grained permissions, searchable, can cross-cut tenants and applications, can manage permissions between users and entities or entities and entities | Requires proprietary APIs to manage, no inheritance of permissions, need lambda API call to add membership to tokens |
| [Entities And Grants](#entities-and-grants) | Fine grained permissions, searchable, can cross-cut applications, can manage permissions between users and entities or entities and entities | Requires proprietary APIs to manage, no inheritance of permissions, need lambda API call to add membership to tokens |
| [User.data](#the-userdata-field) | Searchable, arbitrary JSON that you control, easily added to tokens | Pure data so all authorization decisions need to be made by your application, need to be careful with data types |

### Tenants
Expand Down
Loading