• Describe the security functionality your system utilizes and how these capabilities are supporting at all levels (process, step, document, field, etc).
…The system is role based. Roles will be mapped to case types, whereby the case type defines what document types (business objects) and properties (fields) are visible. If they are visible it is defined how they behave in what state, i.e. read-only, editable or insert able.
• Is the concept of role supported?
…Yes.
• Can users authenticate using Single Sign On (SSO) technologies? What is the level of effort in setting up Single Sign On?
…Yes but this is only available in the Enterprise Edition. The effort to set-up depends on the customer requirements but because of rich set of already available services and libraries it is normally not more than 4 weeks for one person.
• Describe how your system integrates with internal user data sources and/or user directories.
…This is not applicable for the Cloud Editions. The Enterprise Edition is normally based on customerís data sources or active directories data. The internal BIMIXS system requires not only user data, but also organizational entity data being able reflect the customerís organizational structure virtually. Without this information, it is not possible to guarantee no loss of Cases or Talks. Systems which are only based on active directory information cannot fulfill this fundamental requirement. This is why the BIMIXS system normally is based not only on active directory data but also on CRM or HOST data.