Can you place a type of competence in more than one category?
No, for now how it works is that you create the competence and then you select that specific category that you want to link the competence to.
If you want to link it to several categories, you will need to duplicate the competence, and then somehow in the name of the competence itself, make it clear which category it was linked to, but within creating the competence itself, you cannot link it to various categories.
Is competency approval a single person, single-step process, or can multiple approvers be configured?
Essentially you can configure more than one competence coordinator, and each of these will see everything on their dashboard.
Users who are configured as a competence coordinator will see in the competence coordinator section, the competencies that are pending their approval. And any one of them can sign off.
Is it possible to define the order of importance of category per type of user?
You can order around the competencies within the competence matrix as such, but you cannot define within the competence on a user level, which one is more important for one user than the other. However, it is possible to see on the listing page of all users, which users have which competences. You cannot really say that one specific user needs to have a specific set of competencies, you just do it on system level.
Will the CV be viewable by all users of Scilife?
No, only those users that have been configured within the system that they can create, edit, and delete users, (which typically are either admins or managers) will be able to access to CVs and competencies.
And then you need to be a coordinator to be able to edit and change the CV or the competencies, you need to have additional permission to do that. The people that can manage users can at least see the CVS and competencies, the competence coordinators can also modify the CVS and competencies for a user.
Can CV fields be classified as "internal" or "confidential" (for internal purposes only) versus "public" (to be shown to auditors and customers)?
Since the system provides the variables for every time you create a new field within the system, you can indeed set up two different types of Cvs, on document type level so that you can have a CV that includes all those fields that you only want to have shown for internal use and then, another CV type or a CV document type where you include the fields that can also be shown publicly.
Can the CV function be linked to a form used in the recruitment process for easy transfer?
Absolutely, all integrations with external systems as recruitment forms are possible, it just needs to be created or set up, but indeed everything is API driven in Scilife.
If the competence coordinator makes changes to the CV or competencies, does the user need to approve the changes?
No, if a CV is said to be approved after the user has updated either the CV or the competencies and the competency coordinator makes any edits afterward, then no approval is needed on the user end.
The approval is upwards and not downwards right now. But if you think, we would like to have it downwards as well, reach out. It's not something that has been required so far, but it's an interesting point for the future.
