inQuire2 v3
 |  Description | |  Downloads | | Product details | | References | | Service companies | | Screenshots | | Product comparison | | Product website |
How is the system technically protected against access from others?
All access to all pages, including the system pages used to administer the system on the web are protected by authorisations called "collections" (and the users membership of them).
By default when a user visits an inQuire2 site they automatically become a guest. If they login they typically gain extra privileges.
The system checks whether the user can perform the action they are requesting upon each request to the site, i.e. to view a page, administer users etc... If they do not have enough privileges they will be shown an appropriate "can't access" or "security violation" page. Are there pre-defined groups within a role concept?
The main focus is of groups (known as "collections" in the system). A user can be a member of a collection and a collection is used to authorise the various pages. Can the groups within a role concept be freely defined?
Yes. The role is entirely theoretical; there is nothing enforce by the system.
For example, if you want to make it so that only "news editors" can submit "news articles" then you would create a "News Editor" collection and then use this collection to authorise the "News Article" template Which kinds of notification to individual employees does the system know?
Any user who logs in can subscribe to the system to be notified about changes to any pages (documents) within 1 or more categories. The notification takes the form of an email which can be be customised.
In addition content can be placed in "queues" to await (amongst other things) authorisation. Users can then ask to be notified about content put in these queues. This again takes the form of an email. Is there an authorisation cycle which is defined or can be freely organised for publications on the website?
The authorisation cycle can be defined or freely organised depending on how the site is configured.
Content can either be authorised immediately after creation and/or be placed into a queue. The process of putting content in a queue will cause it to appear in authorised users workflow. Is there a protection against inadvertent simultaneous access of several people to one document?
Yes. Only 1 user can be editing a language version at any one time.
For example, if a page is available in English and in French, only 1 user can be editing each language at any one time. A single user could however check out all of the available languages. Which kinds of system-internal task lists and status information are there?
The system provides a "Workflow" area.
Here a user can see content waiting in queues to do things such as translate, authorise, categorise etc...
In addition they can view content they have checked-out and content which has not be categorised yet (or has become uncategorised). Are authorisation procedures supported?
Yes. An "authorisation" queue can be created where content can then be placed to await authorisation.
This can procedure can be used to allow public users to submit content but not allow it on the site until it has been checked. [Basic information] [Asset managament] [Availabilty] [Expandable] [Import] [Performance] [Personalisation] [Reports] [Workflow] [XML] | | Description | | Downloads | | Product details | | References | | Service companies | | Screenshots | | Product comparison | | Product website |
| 
