Every Hyland Cloud solution needs to have its Customer Security Administrator (CSA) - a person authorized to approve potential changes to their hosted solution or to receive protected solution-related information from Hyland. This individual will also receive notifications related to maintenance, security or service failures.
Additionally, Hyland Cloud OnBase CSAs have access to the Cloud Portal, where they can manage their hosted solution and e.g. restart services, view billable storage or manage files waiting for import on a solution’s processing server.
How many CSAs should you have?
Even though one CSA is our minimum, we recommend having at least 2-3 or even more, in case the solution is complex and with international scope.
Why is this so important?
Since CSA’s approval is necessary to proceed with changes to the hosted solution, their unavailability may cause serious delays. Make sure that your organization has at least a few designated CSAs and take regular reviews of the list. For security reasons it is necessary that a person who is no longer at your company is removed from the list immediately.
To request changes, please submit this Cloud Platform Configuration Request: “Add or Remove CSA or FNC” via Community.
How is a CSA different from FNC?
Failure Notification Contact (FNC) is a person authorized to receive notifications about maintenance windows and security/service failures. This individual cannot authorize solution changes and has no access to the Cloud Portal to perform admin tasks.
Useful option: While CSA set-up requires a named individual with a personal e-mail address, FNC can be set up with a group e-mail address too.
More about Cloud Platform Configuration Requests can be found here.
For a complete description of roles and responsibilities, please check this article.
