If you're an administrator using CompetencyCore for the first time, this is a great place to get started. Before walking through the first steps, we'll give you a quick tour of the help center:
Get started in six steps:
- Personalize your site
- Create library content
- Build jobs or copy jobs from templates
- Add users
- Set up the org structure
- Assign permissions
1 Personalize your site
Upload a logo and fill out your company information to brand your CompetencyCore site.
- Click the gear icon on the top right of your screen.
- Click Settings in the Administration menu.
- Select Company under General Settings.
- Upload a logo, enter your company details, and click Save.
2 Create library content
Libraries are containers for the building blocks of your site. All of the content and activities in CompetencyCore are built using these items stored in libraries:
- Knowledge Areas
- Working Conditions
- Additional Information
3 Build jobs or copy jobs from templates
Jobs are built using items from the libraries on your site. This includes competencies and job description items. There are two ways of setting up jobs:
- Build jobs using content from libraries.
- Copy pre-built jobs from templates.
Job templates are read-only versions of jobs purchased from the marketplace. They're stored on a separate page in the Jobs module so you'll always have access to the original version of a job. Copy a template to create an editable version of the job on your CompetencyCore site. The templates are a point of reference, but the copied versions are what you'll be customizing to reflect the jobs in your organization.
4 Add users
Users are people with CompetencyCore accounts. You can create accounts for each employee in your organization or import accounts in bulk.
5 Set up the org structure
- Positions define the structure and hierarchy of your organization. A position is assigned to a user and to a job.
- Departments are containers for positions. Put positions in departments to organize them.
- Teams are not about reporting hierarchy; they're containers for users. For example, a team could have members from multiple departments who are working on the same project together.
6 Assign permissions
A security profile is a list of permissions such as 'Manage Libraries' or 'View Jobs'. Each profile has different permissions turned on or off. A profile can be assigned to users, positions, departments, or teams. If a security profile is assigned to a department, its permissions apply to all positions in that department.
Your site comes with two default security profiles:
- Administrators Security Profile: for HR administrators who manage the site or create content.
- Regular Users Security Profile: for employees accessing the site to view content and perform tasks like taking an assessment. This is the default profile assigned to all users.