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

Tenant provisioning, show and fix-up #199

Open
elv-serban opened this issue Dec 3, 2024 · 1 comment
Open

Tenant provisioning, show and fix-up #199

elv-serban opened this issue Dec 3, 2024 · 1 comment
Assignees

Comments

@elv-serban
Copy link
Contributor

elv-serban commented Dec 3, 2024

Provisioning:

  • add one more mapped group tenant_uses (called acme - Tenant Users)

  • permissions

    • tenant contract fabric object
      • 'manage' permissions for the group Tenant Admins (attention - the tenant contract may not allow this!)
  • create content_ops and tenant_ops users (acme_content_ops and acme_tenant_ops)

    • set tenant ID
    • content_ops - member of group Content Admins
    • tenant_ops - member of group Tenant Admins
  • add funding user in authd (maybe optional?)

Show:

  • show all 3 mapped groups: tenant_admin content_admin tenant_users
  • show permissions for the Tenant object (groups with permissions)
@elv-sam
Copy link
Contributor

elv-sam commented Jan 24, 2025

A few tweaks I made for the new tenancy that we could add to auto setup:

  • Add content ops key to Tenant Users group
  • Add tenant ops key as manager of Content Admins group
  • Set default metadata on marketplace and event site objects (otherwise requires a save in fabric browser for each object, to initialize them)
  • Set tenant, marketplace, event site objects to Listable, live stream site object to Viewable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants