Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Users
Users are at the core of Employee Success. Although completely integrated with Jira, Employee Success needs to create its own entries in the database for users and their attributes. This data is then utilised in the system to segment users into groups based on different attributes.
| Note | ||
|---|---|---|
| ||
| Users who are deactivated or deleted from Jira will be automatically marked as inactive or deleted within Employee Success. Since these users cannot login in Jira anyway, we don't provide an option to remove them from Employee Success. |
Roles
Each one of the users in Employee Success company directory will either hold a role or will have 'no access' to for Employee Success. At any given time, one user can have only one role.
| Note | ||
|---|---|---|
| ||
| Do keep in mind that role defined under Employee Success company directory is limited for its features, it won't have any bearing on Jira features or features of any other addon. |
Designations
Also called as Job title, designation is an attribute associated with each user of this app. One user can have only one designation at a time. By default, Employee Success comes with HR Manager, Product Manager, Project Manager, QA Engineer, Software Developer designations. This list can be easily managed to better match your organisation needs. This is an optional attribute. User can very well exist in the system without a designation.
Managers
Manager is someone to whom a given user reports to. To make Jon Doe manager of Jane Doe, both of them must already exist as Employee Success users. One Employee Success user can have only one manager associated. This is an optional attribute. User can very well exist in the system without a manager.
Teams
Team is a grouping of users based on their functional areas or organisational strategy. Teams in Employee Success are a special entity which act as containers for users. One team can have one team lead & multiple users as team members. Any given team can have one parent team & one or more children teams. This allows Employee Success to create an org hierarchy chart to better help you visualise structure.
Team Type
There is an additional attribute called team type. It lets you treat any team as a group. By using types, you can create multi-level hierarchy for example Department -> Division -> Team -> Sub-team. In essence, Employee Success will treat everything as a Team, whether they are a department or a division or something else will depend on what type they are of.
| Note | ||
|---|---|---|
| ||
Note that one Employee Success user can be a part of more than one team. |
Team Lead
Team lead is a special type of team member. There are configurations across features that give special permissions to team leads such as being able to create team level OKRs for the team they are leading.
| Info | ||
|---|---|---|
| ||
Employee Success will be further enhanced so that team leads have additional permissions such as managing their own team, creating review forms for them etc. |
On this page
| Table of Contents |
|---|
In this section
| Child pages (Children Display) | ||
|---|---|---|
|