Jeto Ideas

Let us know what you want to see next in Jeto!

Control permissions on a user basis, not just on Launcher basis

Feature like Auto-Schedule or List selection are currently controlled on a per launcher basis.
It would be better if it was controlled on a per user basis. Allowing the Admin to determine the level of access per users would allow them to mange more efficiently who can do what in Jeto. It could be managed by the "level" of that user. 

A specific example: 
Mark is advanced user, so the Admin want him to be able to send auto-scheduled campaigns, no matter which launcher Mark uses. 
Steve is a new employee, so the Admin do not want Steve to be able to create auto-schduling campaigns fo rteh moment, but he wants Steve to use the same Launcher than Mark.

  • Alexandre Pelletier
  • Sep 19 2018
  • Attach files
  • Admin
    David Desrosiers commented
    December 12, 2018 18:48

    @alex Do you have client name I can tag on this request?

    This requires an in depth review of roles and permissions which we do see as a key element to deploy in larger teams.  Although we will likely not be able to address this the next 0-3 months we will definitely work on more advanced roles and permissions in the near future. 

    I'd love more input on how you see those permissions being set at user level. I see 3 possible options:

    1) Same permissions per user across all Launchers
    2) Launcher per Launcher for each collaborator individually
    3) Default settings at launcher level, with overwrite at User level (enable Automated Launch for this User. In this case both conditions must be met for Campaign to go in Auto-Launch.



    Thanks 

    David