We need to Limit User who will be able to create, run and modify NCM Jobs created by only themselves.
But, should not be able to View/Modify Jobs created by Other User.
This role is not available in current NCM versions.
Case # - 00283864
Not sure, if the option available in Account Limitation. Did you check once if account limitation has any option to select the NCM Jobs?
Thanks.
Yes, I have checked, there are different NCM roles out of which 'Administrator' and 'Engineer' role can only access NCM jobs, however all NCM jobs can be accessed/ modified/ deleted which cannot be restricted.
Correct. There is not a role which would would limit access or visibility to jobs. It seems what is being looked for here are jobs may be like limitation placed on nodes.
to restrict only to jobs one creates, may cause other issues. The jobs are really structured by author. The author is not necessarily one that created the original job, it would change based on the last person to edit the job. even for a time change.
then the person that created the job would no longer be able to see the job.
this is a valid request and is particularly applicable to MSP or other really segregated environments.
Maybe the if there could be a way to tag a job to limit visibility based on users might help and not the author.
I assume that this means that you would segment this by user and then by type of user. So a 'super admin' could view all while a standard admin would be segmented to their individual portion of the network?
Are there any additional expectations/details you would add to this request?
Right, jobs created by one user should not be modified by another user, only super admin can access all jobs.
I am thinking for alternate solution . If you allow user to view only set of devices via Account limitation and set NCM role to Engineer.
Hope this will work for you. Little bit extra efforts
yeah i have tried using Engineer view, however it's not working.
In this case we want to limit NCM jobs section. He should be able to create job, add any devices for job processing. Only the thing is, Jobs created by User A should not be accessible to User B, except Admin.
Hi,
I replicated this on 2019.4 platform and it's limiting the account to only select the objects you assigned on account limitation but yes it is still showing the other jobs and if you ran a job that's already created it still runs it to the original nodes assigned to the job.
We should really have a feature to limit jobs per user except Admin etc.
Hopefully this feature will be implemented.
My issue is I have an installation of several hundred switches in NCM. I also have 3 or 4 admins who create and run jobs. But as we make jobs to run changes, or upgrades, we tend to copy other folks jobs. Maybe we overwrite it instead of duplicating it, etc. So I end up with 30 jobs where I only have 6 or 8 that I care about. I want the ability to do per-user jobs and world-usable jobs...or at least world readable jobs that I can duplicate in my area.
This needs some attention. If a user has access to manage any job, they can manage all jobs. This doesn't play well in a multi-tenant environment.