Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


Guest
2008-09-03T22:03:17Z
1. Ability to select which JOBS a user can see & access. In a JOB you would have a Security tab with these options:
a. Default - Checked checkbox to work as currently designed, which treats all job as equal based on configured permissions.
b. Custom - Uncheck the checkbox and a list of configured users would appear. From here you would add only the user to have access to the job (their access would be based on how they
are configured in the “Manage User Permissions” window.
2. If a user does not have any permissions on a JOB, the JOB would not appear when they connect the VisualCron Client
3. In the “Manage User Permissions” window you would have a checkbox next to the “Active” check box to select the user as a global Admin. This would override any of the permissions to make it so
that the user would be a global administrator. This would prevent your admin account from getting blocked out especially if you forget to add your account access to the job when you select the
custom checkbox.
4. Another useful user permission would be "Inactivate/reactive" for both a JOB & TASK. This would allow a user to control the option in the right click context menu of Jobs & Task. Currently you have to
have edit permissions to do this. This option would be located on the "Permission" Tab under the permission Jobs & Tasks in “Manage User Permissions”


NOTES: Removed the task level permission suggestion. Job level access control is much more important because it overcomes the obstacle of user access delegation on a server being all (Jobs) or none. This would allow an administrator the flexibility to actually consider the delegation of control because they will be able to limit a user to specific jobs only.


Sponsor
Forum information
adutoit
2008-09-04T11:29:52Z
There has been talk by the developers about new "enterprise" features planned for VC; I really hope that security is addressed in a big way. What you are requesting has been regurgitated in different guises in the forum a number of times. The ability to group jobs, assign users to those groups; preventing a non-admin user from stopping the VC service;AD integration; would go along way in securing VC. In our experience of rolling out VC, the biggest concern has been how to control access to jobs.
Support
2008-09-07T13:34:45Z
Please list all permissions in detail here that you would like to see on Job level.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2008-09-07T18:50:14Z
I think it might be to complex for the user to handle those things at Task level. We have to keep some boundaries otherwise the complexity and boundaries will be to large to handle.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2010-07-23T17:21:24Z
Please continue discussion here and test this version:

http://www.visualcron.co....aspx?g=posts&m=6509 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2012-05-11T11:14:35Z
We are currently developing this and need your feedback - please continue discussion based on the Google document in this thread:

http://www.visualcron.co...aspx?g=posts&m=12045 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2012-06-07T09:48:08Z
Version released with group and Job permission support:

http://www.visualcron.co....aspx?g=posts&t=2505 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top