Skip to main content

Main - User Permissions​

User permissions control who can log on to a VisualCron Server and what each person can do there. Use this page to add users and Active Directory (AD) groups, to put users into groups, to set what each group may do, and to give a group different rights on one Job, Credential or Connection.

Users and groups​

A user is a user name and password that can log on to the Server. Permissions are not set on the user. They are set on groups, and a user belongs to one or more groups. A user can do something if any of their groups allows it. A user who belongs to no group can log on but cannot do anything.

Users can be internal VisualCron users, or AD users who log on with their Windows account. See Active Directory logon.

You manage users and groups in two windows:

  • Server -> Main settings -> User permissions: users and AD groups
  • Server -> Main settings -> Group permissions: groups and their permissions, in the Manage group permissions window

Every user who belongs to a group can open both windows, because Read on User permissions is always granted. Adding, editing or deleting users and groups needs Add, Edit or Delete on User permissions. Your own user is an exception. The desktop Client lets you change its name, user name, email and password without Edit. The Server accepts changes a user makes to their own user record, including group membership, from programs other than the desktop Client.

warning

A new Server has the user "admin" with no password, in the Administrators group. Set a password for it right after you install VisualCron, or create your own administrator user and then delete "admin".

The Server creates "admin" again, with no password, when no users remain: at the next start, or after an import that leaves no users. Keep at least one administrator user. If "admin" appears again, set its password at once.

The user list also has a built-in user for the VisualCron tray client, in the group VisualCron system group (limited). It can log on only from the Server computer. The Client does not let you edit it, and the Server creates it again if it is missing. Leave it as it is.

Active Directory logon​

By default, users log on with an internal VisualCron user name and password. To let users log on with their Windows account, two settings are needed:

Server -> Main settings -> Settings -> Users/Logon

Users/Logon tab of the Settings window with Only allow local connections, Allow Active Directory Logon, AD Server, the Credential list, Test, SPN and UPN

File -> Manage servers -> Add

Add/Update server window with Use Active Directory logon selected under Credentials

The User permissions window​

The window has two tabs:

  • Users: internal users and AD users
  • AD groups: the AD groups whose members may log on

A green check icon marks an active user or AD group, and a red cross marks an inactive one. An inactive user cannot log on.

On the Users tab, the columns are User name, Name, AD (whether this is an AD user), Email, Domain, AD host name, ExpiryDate and Blocked. ExpiryDate is the date the password expires. When password rules are off, it shows 12/31/9999.

The toolbar buttons Add, Edit, Clone, Delete and Audit log act on the tab that is selected. Clone opens a new user (or AD group) filled in with a copy of the selected one, groups and password included. Change the user name and enter a new password before you click OK.

Right-click a user for more actions:

  • Deactivate / Active: turns logon off or on for the user
  • Block / Unblock: blocks logon for the number of minutes in Lock account for on the Password rules tab of the Settings window. Blocking applies to internal users only. If Lock account for is "0", the block ends at once
  • Update password: shown on your own user when you cannot edit users, so that you can change your own password
  • Audit log and Versions..: show the changes made to the user

Server -> Main settings -> User permissions

User permissions window, Users tab, listing two built-in users with the User name, Name, AD, Email, Domain, AD host name, ExpiryDate and Blocked columns

Add or edit a user​

Add, Edit and Clone open the Add/Edit user window. It has two tabs, Credentials and Groups.

Server -> Main settings -> User permissions -> Users -> Add -> Credentials

Add/Edit user window, Credentials tab, with Is AD user, Use permissions from AD groups, Name, Username, Password, Email, Active and Expire

Is AD user (click on Search button to add AD user)

Checked when the user is an AD user. You cannot check it yourself. Click the Search button next to Name: and select the user in Active Directory, and the box is checked for you. For an AD user, Name:, Username: and Password: cannot be edited.

Use permissions from AD groups

Available for AD users only. When checked, the user gets the groups of the AD groups they belong to (see How AD users get their permissions), and the Groups tab is unavailable. When cleared, the groups checked on the user's own Groups tab apply.

Name:

The display name, shown in the user list and in the Server log.

Username:

The name used to log on. It must be unique.

Password:

The password used to log on. When Implement password rules is on (Password rules tab of the Settings window), a password you enter must meet those rules. An empty password is still accepted, so always enter one.

Email:

The user's email address. For an AD user created at first logon, it is filled in from Active Directory.

Active

When cleared, the user cannot log on.

Expire

note

Expire saves the user and closes the window at once. Click OK to save any other changes first, then open the user again and click Expire.

Marks the user's password as expired. The desktop Client then asks an internal user for a new password at the next logon, but only when Implement password rules and Force user to change the password the first login are both on (Password rules tab).

Groups tab​

Check the groups the user belongs to. For a new user, the default group for new users is checked for you. On a new Server, that is Administrators, which has full rights. Clear it unless the user needs full rights (see Default groups). If no group is checked, the Client asks you to confirm before it saves the user.

Add an AD group​

On the AD groups tab, Add opens the Add AD group window. Members of an active AD group listed here may log on, with the VisualCron groups you choose for it.

Server -> Main settings -> User permissions -> AD groups -> Add

Add AD group window, AD group tab, with Group name, Active and Let users inherit (not clone) permissions

The AD group tab has these fields:

Group name:

The AD group. You cannot type it. Click the Search button and select the group in Active Directory.

Active

When cleared, members who follow their AD groups can no longer log on through this AD group or get its groups. Users who got a copy of its groups (see the next field), and AD users with their own groups, are not affected. To stop them, deactivate or delete them on the Users tab.

Let users inherit (not clone) permissions

Checked by default. Decides how a new AD user, created when they first log on, gets their permissions:

  • Checked: the user follows the AD groups they belong to, and Use permissions from AD groups is checked on the user
  • Cleared: the user gets a copy of this AD group's VisualCron groups once, and after that keeps their own Groups tab. The user can then log on even after they leave the AD group, or after the AD group is deactivated

The Default VisualCron group(s) tab lists the VisualCron groups that members of this AD group get. For a new AD group, the default group for new users is checked for you. On a new Server, that is Administrators, so every member who logs on would get full rights. Clear it unless they need them (see Default groups).

How AD users get their permissions​

When an AD user logs on, the Server finds the user in Active Directory and reads their AD group membership. Then:

  • The user is already on the Users tab:
    • an inactive user is refused
    • with Use permissions from AD groups checked, the user must belong to at least one active AD group on the AD groups tab, or logon is refused
    • otherwise the user's own groups apply, and their AD group membership is not checked
  • The user is not on the Users tab yet:
    • the user must belong to at least one active AD group on the AD groups tab, or logon is refused
    • the Server then adds the user to the Users tab as an AD user
    • if any of the user's active AD groups has Let users inherit (not clone) permissions cleared, the user gets a copy of that group's VisualCron groups. Otherwise the user follows their AD groups

A user who follows their AD groups gets the VisualCron groups of every active AD group they belong to. The list is read again at each logon:

  • a change to an AD group's VisualCron groups applies at once, and so does deactivating it
  • an AD group you add to the AD groups tab applies from the user's next logon

Groups​

You can manage groups in two places:

  • the Manage group permissions window (Server -> Main settings -> Group permissions)
  • the Groups tab of the Add/Edit user window, which has the same Add, Edit, Clone, Delete and Audit log buttons

Add, Edit and Clone open the Add/Edit user group window.

Server -> Main settings -> User permissions -> Add -> Groups

Groups tab of the Add/Edit user window listing the Administrators, Viewers and VisualCron system group (limited) groups, with Administrators checked

Add/Edit user group window

Add/Edit user group window for the Administrators group, with Name, Description, Default group for new users, an older version of the automatic rights option, and the permission grid with Read, Add, Edit, Execute and Delete columns

Name:

The name of the group.

Description:

Optional text that describes the group.

Default group for new users

When checked, this group is checked for you when you add a user or an AD group. Only one group can be the default, so checking it on one group clears it on the others.

A clone of the default group has Default group for new users checked, and saving the clone makes it the default. Clear the box unless the clone should become the default.

Auto full rights on new objects

Checked by default. Controls whether members of the group automatically get full rights on the Jobs, Credentials and Connections they create.

When checked, and the group lacks any of Read, Edit, Delete or Execute for that object type, the Client adds an override to the new object when a member creates it. The override gives the group Read, Edit, Delete and Execute on that object. Members can then manage what they create without an administrator granting rights on each new object. When the group already has those rights, no override is added.

This option has no effect for an AD user who has Use permissions from AD groups checked. It applies to internal users, and to AD users who have their own groups.

Use group permissions only (ignore per-object overrides)

Cleared by default. When checked, every override for this group is ignored, both those that grant and those that deny. This covers overrides on a Job (and so on its Tasks), a Credential or a Connection. Only the group's own permissions apply. A group that relied on a deny override gets its own right back. See Override permissions on one object.

To create a group with limited rights, complete the following steps:

  1. Click Server -> Main settings -> Group permissions, and then click Add.
  2. Enter Name: and, if you want, Description:.
  3. In the grid, clear every action the group must not have. Check in particular Add, Edit and Delete on User permissions, and Import settings and Export settings (see Permissions and actions).
  4. Click OK.
  5. Click Server -> Main settings -> User permissions, select a user who needs the group, and click Edit. On the Groups tab, check the new group, clear Administrators unless the user needs full rights, and click OK.

For an AD group, check the new group on the Default VisualCron group(s) tab of the Add AD group window instead.

Permissions and actions​

The grid in the Add/Edit user group window has one row per permission and five actions:

  • Read: view the object, or open its window
  • Add: create a new object
  • Edit: change an existing object
  • Execute: run or use the object
  • Delete: remove the object

Not every action applies to every permission. A grayed-out box cannot be changed: it is either always granted or never granted. For example, Log has only Read.

warning

A new group starts with every box checked that can be changed, except Add, Edit, Execute and Delete on Remote file explorer. This includes Add, Edit and Delete on User permissions, which let a member manage users and groups, and so give themselves full rights. It also includes Import settings and Export settings.

Clear every action the group must not have before you click OK.

For the list of permissions and what each action controls, see Supported Permissions.

Credentials permission​

The Credentials row controls the Manage credentials window and the Credentials a user can work with. For more, see Global - Credentials.

  • Read: open the Manage credentials window. The window, and the Credential lists in Tasks, show only the Credentials the user has Read on, overrides included
  • Add: add Credentials
  • Edit: change Credentials
  • Execute: use the Credential in a run. When a user starts the run, the Server checks Read and Execute on the Credentials row of that user's groups, for each Credential the run uses. That is a single Run Job or Run Task started from a Client, a test of a saved Credential, or a Task run requested through the Web API with a user (Task/Run). Runs started by the schedule or by a Trigger, Run selected Jobs, and Jobs started through the Web API (Job/Run) are not tied to a user, so no check is made. Overrides on the Credential, and Use group permissions only (ignore per-object overrides), are not taken into account for this check. When you run a single Task, the desktop Client also checks Execute on the Credentials row of your groups, even for a Task that uses no Credential. If that check fails, the Client does not start the Task and shows "You are not allowed to use this Credential in this Task"
  • Delete: delete Credentials
warning

If the check on Execute or Read fails, the Server does not use the Credential:

  • a Task that starts a separate program, such as the Execute Task, runs as the VisualCron service account
  • a Task that uses the Credential inside VisualCron fails with an error

Do not rely on clearing Execute to keep a group from running a program with a Credential's rights, because the program then runs as the service account. Also limit who has Edit on the Jobs, and Add and Edit on the Tasks, that use the Credential.

warning

After a Credential is added or changed, the Server sends the Credential to every logged-on Client, including users who have no Read on it. Do not rely on Read to keep a Credential from a user who can log on to the Server. Give logons only to people you trust with your Credentials.

A program runs as the service account​

An Execute Task, or another Task that starts a separate program, ran as the VisualCron service account instead of the Credential's account. The user who started the run lacks Read or Execute on the Credential. Give that user's group Read and Execute on the Credentials row, or let a user who has them start the run. An override on the Credential does not change this check.

A Task that uses a Credential fails when a user starts it​

The Task works on schedule but fails when a particular user runs it manually or as a Task through the Web API (Task/Run). That user lacks Read or Execute on the Credential. Give the user's group both on the Credentials row. An override on the Credential does not change this check.

Override permissions on one object​

You can give a group different rights on one Job, Credential or Connection. In the Job, Credential or Connection editor, click Permissions.. to open the Override permissions for this object window.

The window lists every group with Read, Add, Edit, Execute and Delete. Change the boxes for a group to override its permissions on this object only:

  • a green cell grants what the group's own permissions deny
  • a red cell denies what they grant

Only groups whose boxes differ from their own permissions are saved as overrides.

An override changes the rights of that group only. A user who belongs to another group that has the right still has it.

An override on a Job also applies to the Tasks in that Job. For a group with an override on a Job, the override's boxes replace the group's Tasks row for those Tasks. To add a Task to a Job, the group needs Edit on the Job. The desktop Client also checks Add on Tasks, or Add in the Job's override if the group has one. A group without an override on the Job uses its Tasks row.

A group with Use group permissions only (ignore per-object overrides) checked ignores all overrides.

Overrides on a Credential or Connection decide who can view, edit, delete and export it. They do not change the check the Server makes when a run uses the Credential or Connection. That check uses the group's Credentials or Connections row only (see Credentials permission).

Default groups​

When the Server starts with no groups at all, as on a new installation, it creates two groups:

  • Administrators: every action in the grid, except Execute on Remote file explorer. Administrators is the default group for new users
  • Viewers: meant for monitoring, but not read-only (see the warning below)

Both are ordinary groups that you can edit, clone or delete. A Server that already had groups before an upgrade does not get them.

The group VisualCron system group (limited) is used by VisualCron's own components. Do not assign it to users. The Client does not let you edit or delete it.

warning

Because Administrators is the default group for new users, it is checked for you when you add a user or an AD group. Clear it unless the user or AD group needs full rights, or make another group the default.

warning

The Viewers group is not read-only. Viewers have:

  • Read on every permission, including Server settings, Credentials, Variables and User permissions
  • Execute on Connections and Credentials
  • Add, Edit and Delete on SSH keys

With these rights, a Viewer can:

Some of these boxes are grayed out and cannot be cleared in Viewers, such as Read on Credentials and on Jobs. For users who must not have these rights, create a new group with Add, clear what they must not have (see Permissions and actions), and use that group instead of Viewers.