Request failed with status code 502
Server Error
Server Error
Server Error
Server Error
Server Error
Server Error
Server Error
Server Error
Server Error
Server Error
Server Error
Server Error
Server Error
Server Error
Server Error
Server Error
Server Error
Server Error
Server Error

Online Assessments

Upload questionnaires and send them to your stakeholders for feedback - long

  • Episodes13
  • Duration33m 20s
  • LanguagesEN
Episode 2

Typical OA Questions

Typical questions we get around OAs

Use Cases

The OA module is a generic tool, which means that it can be used for many purposes. In general, every time you want to know something and need to ask questions, this is the right feature to use (at least in eramba).

Since questionnaires are defined by you, the feature is very flexible and can be used for multiple scenarios: Risk, Vendor, Privacy, Consulting, Gap Assessment, Etc.

Portal

People answering your questions will use a separate portal called the "Online Assessment" portal. This portal, while contained in the eramba application, is separated from the "Main" portal (where you typically use eramba).

The accounts you will create to let people access the "Online Assessment" portal will not be able to access the "Main" portal so as long you create them correctly.

Is perfectly normal to leave the OA portal public to the internet so people outside your organisation can provide you with feedback.

Recipients

When you create an OA you will assign one or more recipient accounts, only they will be able to access the OA you have created for them. You do not have to worry about other people being able to access their OAs.

The authentication on the OA portal is defined by you (typically it inherits whatever authentication you have defined in the Main portal). For example, if your Main portal uses SAML, your OA portal will inherit that by default.

Local accounts (those that authenticate against eramba instead of external directories) created in eramba that have been granted access to the OA portal will be able to authenticate (provided their credentials are correctly entered), no matter what authentication you have set on your "Main" portal (SAML, LDAP, Local, etc).

You do not typically need to create accounts in your corporate directory for external people to provide you with access, you can simply create local, temporal accounts in eramba.