Seeking feedback: When a user is working within an...
# proj-automation
e
Seeking feedback: When a user is working within an OpenHands org, should we make all automations visible to all users in the Org, but only editable/changeable by 1) the Org Admin and 2) the original creator of that Automation?
l
IMO no, users will want personal automations that they don’t show to other people, and a large org should hopefully have hundreds of automations so it may be overwhelming. Maybe we could have an explicit sharing switch though?
It’s probably worth looking at the design patterns in other similar products
e
Good point, will do some research. But I think Admins might need to see all of them (in case an automation went rogue). We had a prospect who build 160+ automations (using their own automation framework) and the 'Admin' persona was able to see everything
but there's definitely a few other vendors we can compare to, so will be good to have that data
l
Yeah, I think it’s OK for the admin to see all of them, that makes sense!
➕ 1
c
💯 I think there are org automations and personal automations and permissions to determine who can create each of these.
d
tossing it out there: in google docs users can opt into sharing view/edit permissions on a doc with a certain group of users or the org as a whole. I think there's some parallels there that are worth considering for automations (and, actually, any agent conversations on Enterprise Orgs). and then of course +1 that admins can see (and edit) all 👁️
➕ 1