User Accounts and Security

Here is the new version of this article in the Veracross Community . Overview Each Veracross user account is a member of one or more security roles. These security roles determine which data the user can view and update. Primary roles form the ...

Here is the new version of this article in the Veracross Community. Username Conventions Before creating any user accounts in Veracross, it is important that the username convention for each security role be reviewed to ensure the account userna...

Here is the new version of this article in the Veracross Community. Overview Some schools want to create user accounts in Veracross for Parents of Future Students and Future Students. Typically this is wanted in order to push the user accounts o...

Here is the new version of this article in the Veracross Community. Overview To manage user accounts in batch, navigate to the System homepage in Axiom and click the Action menu.  Only users with the security role of SysAdmin_1 can create u...

Here is the new version of this article in the Veracross Community. Overview Parent and Student portal accounts can be disabled by any System Administrator if needed throughout the year.  To disable accounts, perform either the batch or one...

Here is the new version of this article in the Veracross Community. Overview Email domain security can be added so that Veracross scans emails sent via distribution lists using the DKIM and SPF security protocols. This applies to inbound secur...

Here is the new version of this article in the Veracross Community. Overview Access to data on records in Veracross is controlled by security roles. Users are assigned security roles based on the level of access and update privileges they need i...

Here is the new version of this article in the Veracross Community. Overview The EU General Data Protection Regulation (GDPR) — designed to harmonize data privacy laws across Europe, to protect and empower all EU citizens data privacy and...

Here is the new version of this article in the Veracross Community. Overview The actual granting of VCA access is done by the Account Manager, but the school should ensure that the person already exists in Veracross as a staff or faculty, has a ...

Here is the new version of this article in the Veracross Community. Overview User Impersonation is a feature that allows system administrators and certain staff members to log in as another Veracross user for testing purposes. Impersonation is s...

Here is the new version of this article in the Veracross Community. Overview The Identity & Access Management homepage in Axiom gives quick access to user accounts, security configuration, and logs. Homepage Sections User Accounts: Prov...

Here is the new version of this article in the Veracross Community. Overview Veracross can authenticate with Microsoft’s Active Directory server to achieve Single Sign On. Single Sign On allows end users to use their primary network (Activ...

Here is the new version of this article in the Veracross Community. Overview Multi-factor authentication can be enabled for accounts accessing Axiom and Portals. Multi-factor authentication (MFA) is a security mechanism that requires access to m...

Here is the new version of this article in the Veracross Community. Overview Schools have a number of options available for managing password expiration for each of their users: Per User Change the user’s account status to “passw...

Here is the new version of this article in the Veracross Community. Overview In order to have Veracross authenticate users against a school’s Active Directory server, a few things need to be set in place before AD Authentication can be ena...

Here is the new version of this article in the Veracross Community. Overview Schools using Google Apps for Education/Non-Profits can enable single sign-on (SSO) — part of the extra-cost Google Authentication module — so that their co...

Here is the new version of this article in the Veracross Community. Overview User Account naming conventions can be set per security role.  Using the “Security Roles” link on the System homepage, all security roles can be access...

Here is the new version of this article in the Veracross Community. Overview Security roles determine homepage access in Axiom. This article details the homepages to which different security roles have access by default. SysAdmin_1 (read/write...

As an additional security measure, Veracross has implemented the use of reCAPTCHA on login pages for both Axiom and all Portals.

You can now create OAuth applications for vendors using Veracross. OAuth applications allow for vendors to use Veracross OAuth SSO to enable login to their vendor applications. This can provide a few benefits for Veracross end users

Creating OAuth Applications will be necessary to enable Single Sign On (SSO) for vendors working with your school. Creating OAuth Applications is a self-serve workflow, and doesn’t require approval or involvement from Veracross Support.

Because OAuth is a standard approach for enabling SSO, there is a lot of material on the internet about how to set up an integration with an OAuth provider.

Here is the new version of this article in the Veracross Community. Overview You can now use Okta as a third-party authentication method when accessing Veracross through Axiom or Portals. Setting up and using Okta for authentication incurs no...