You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that currently, there are only two type of users (Super Administrators and Administrators). And without being SuperAdmin, there is no way to share lists and campaign, right?
We would like a way to let user A access lists created by user B, and vice-versa. In short, adding users to a group/team which would share all resources attached to it, without being SuperAdmin themselves.
The text was updated successfully, but these errors were encountered:
Yes, interesting. I guess with the current admin arrangement that's not easy. Maybe for now, each team has a shared login. Maybe we can make the "admin" in the system more like a team and have different logins associate with that team. That's not a trivial change though.
Yes, for now we will use a single shared login. I guess most organization do like that today (or maybe they deploy several instances, but that's overkill and a pain to maintain)
As I see it (but I have not digged into the code), it could also be done by adding a field "team" (or maybe better, "teams") to each objects (Lists, Campaigns, etc.) and admins (it would be useless for Super-admin, they would still see all and everything), and allow their access only to matching admins.
It seems that currently, there are only two type of users (Super Administrators and Administrators). And without being SuperAdmin, there is no way to share lists and campaign, right?
We would like a way to let user A access lists created by user B, and vice-versa. In short, adding users to a group/team which would share all resources attached to it, without being SuperAdmin themselves.
The text was updated successfully, but these errors were encountered: