you can TOUCH the relationships to recreate if not present, or otherwise do nothing

just wanted to let you know that we tried running our tests against the latest SpicedDB version built from the main branch and our intermittent issues are gone now, thanks very much!

Are there any dashboards (or any in development) to help with viewing/assigning permissions/relations?

you mean to edit the relationships themselves?

View and/or edit - I was wondering if either officially, or unofficially, someone has built out more of an admin dashboard that wraps the zed client. Somewhere we could go and see the current state of the graph or view/edit relations, etc

not AFAIK

no worries, I figured it may be useful if you need to debug a permission check or something like that as the graph begins to grow larger

I agree. file a proposal?

sure, will do!

could also be its own distinct project, since the API provides all the info necessary

I'm trying to wrap my head around this global admin example: https://docs.authzed.com/reference/schema-lang#global-admin-permissions

this still requires you to define every resource upfront and manage relation ships for them all.

is there a way to get around that? I would rather have the super admin be a yes/no switch for the

platform

in this example rather than a yes/no switch for each resource in the platform

the

platform

is effectively the thing I care about. but if it means I have to keep a list of resources in sync in spicedb, the benefit starts to drop off pretty quick

yeah the zanzibar model has you querying against the thing you are trying to protect

so like

can user:jake view document:123

which might traverse through a platform object, and it may turn out that jake can view it because he's a super-admin

but you have to create the relation between document:123 and the platform?

now, if you don't want to do that, you could also just ask:

can user:jake admin organization:123?

or

can user:jake super_admin platform:yourcompany?

yep, you have to add edges to the graph in order for them to be walked

the later is more of what I'm after

right

thats the one I think I want.

but if I want the implicit trickle effect, I do have to define relations for all resources

yep, but sometimes your document will roll up through an intermediary, which you might have needed in your hierarchy anyway

so you're not writing extra relationships just for super-admin

e.g.

doc->folder->folder->organization->platform

you would only need the

org->platform

extra edge because the rest of the hierarchy is inherent in the permissions model

I'm looking to get a list of definitions, relations and permissions from my schema into a portable format like JSON without having to write a custom parser. Any ideas on the best way I could do that?