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

Add roles system for teams and agencies #535

Open
adriaanvanrossum opened this issue Feb 25, 2021 · 6 comments
Open

Add roles system for teams and agencies #535

adriaanvanrossum opened this issue Feb 25, 2021 · 6 comments
Labels
2021 November 2021 October customer request Tasks created by customers via our website marketing Everything related to marketing prio Do this first
Milestone

Comments

@adriaanvanrossum
Copy link
Contributor

No description provided.

@adriaanvanrossum adriaanvanrossum self-assigned this Feb 25, 2021
@adriaanvanrossum adriaanvanrossum added this to Features & bugs in Public roadmap via automation Feb 25, 2021
@adriaanvanrossum adriaanvanrossum changed the title Add new roles Add roles system for teams and agencies Feb 25, 2021
@adriaanvanrossum adriaanvanrossum added customer request Tasks created by customers via our website marketing Everything related to marketing prio Do this first labels Feb 25, 2021
@adriaanvanrossum adriaanvanrossum added this to the Important milestone Feb 25, 2021
@adriaanvanrossum adriaanvanrossum moved this from Features & bugs to Planned in Public roadmap Apr 6, 2021
@jibsaramnim jibsaramnim moved this from Planned to In progress in Public roadmap Apr 13, 2021
@adriaanvanrossum
Copy link
Contributor Author

adriaanvanrossum commented Jul 5, 2021

@jibsaramnim Related: #494, #262

The why behind it is, there is a couple of people I want to give data to for instance for this month but I don't want them to have access fully to my account and so on.
Either that or different permissions for an account would also work.

Would also be nice if people can give developers access to install the script. Would be nice to give a time limit to it as well. To give a developer access for 30 days for example. Permissions will be automatically deleted after that period.

@adriaanvanrossum
Copy link
Contributor Author

This is how the user interface could look:

Screenshot

@jibsaramnim
Copy link

@adriaanvanrossum a few thoughts:

  • the mock-up does not include a way to actually specify the "all except .." functionality, could you mock something up for that too?
  • the mock-up does not include a way to add more than one website permission, unless the customer should manually write out the same email address multiple times, once for each site, but the "website(s)" column name suggests more than one site can be listed out (per row). Do you have any ideas on how to handle that?
  • the mock-up mentions account (ie. "..who has access to this account"), but this should probably refer to team instead, right? I just want to make sure I am following your thinking exactly right here.

Thanks for this!

@adriaanvanrossum
Copy link
Contributor Author

Thanks for the feedback @jibsaramnim! I updated the screenshot to include those comments:

Screenshot

Regarding account vs team. Does our customer know the difference? Would they know they can have multiple teams? How can we make it clear for them?

@jibsaramnim
Copy link

Right, the original idea --as far as I understood it, anyway-- was to have a UI for creating and managing teams, too, including subscriptions per team, et cetera. This too would have to exist in some form for anyone that has been invited to someone else's team (or teams, plural), especially if they have been granted the admin/finance role for example. They would have to have a way of being able to see all teams they are part of, as-well as visit each team's settings (if permitted).

@adriaanvanrossum
Copy link
Contributor Author

Some extra info from a potential agency customer:

Hi Adriaan, I think your prices are perfectly justifiable; so I think they are good. I think there should be the choice of the following;

  • From your Agency dashboard you add a website/customer;
  • You may or may not give him access through his own account (not all of our clients need to)
  • Invoicing is done via the client (specify on property level) or via the Agency account (two options). If we can invoice the client ourselves then for example there is a revenue model for us.

In that case the Agency dashboard is more of a sales funnel for you guys. The easier it is for us to sell and manage this to clients; the sooner we will start doing that. The use of the dashboard itself should then have no cost (but maybe have a minimum of 5 properties or something like that) From the Agency dashboard you easily log in as a client to see his statistics. You also easily go back to your dashboard to create or change a new property.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2021 November 2021 October customer request Tasks created by customers via our website marketing Everything related to marketing prio Do this first
Projects
Public roadmap
  
In progress
Development

No branches or pull requests

2 participants