Core concepts
Users, teams and escalation chains
What Srishti keeps about each person, how teams and escalation chains work, and what happens when you edit or remove someone.
- Admin
Everyone who uses Srishti is set up in User Management: their sign-in email, their team, what they can open, whether they approve, and who their late work escalates to. Getting these right is what makes the rest of Srishti work: the team decides which activities a person can own, and the escalation chain decides who hears when their work slips.
Changing anything in User Management needs User Management: Action.
People
People on one tab, the teams they belong to on the other.
Find a person, or narrow the list with All teams and All project types.
Opens the form for a new person.
One pill per module the person can open, with View or Action. Modules set to None are left out.
Who this person's due and overdue work escalates to. — (top of chain) means they have no L1.
Change anything about the person. The bin next to it removes them.
- Name
- As others see it in Srishti.
- Email ID
- The person's company Google account (@kapiva.in). Srishti has no passwords: this is how they sign in.
- Team
- Required. An activity's owner is picked from the activity's team, so someone on the wrong team cannot be given that team's work.
- Page access
- What the person can open: Portfolio (None or View), Projects, Templates and User Management (None, View or Action), and My Activities, always Action. See Page access.
- Project types
- A label for filtering the user list only. It gives no access to any project.
- Approver
- This person is an approver. Lets them be named as a project's baseline approver, decide activity approvals, and be someone's escalation contact.
- Escalation level 1 and 2
- Who this person's late work escalates to. See Escalation chains.
Escalation chains
Each person has up to two escalation contacts. When their activity is due, their Escalation level 1 (L1) is told; four days after the due date, their Escalation level 2 (L2) is told, or their L1's own L1 when they have no L2. The full schedule is in Notifications, reminders and escalations.
- Escalation contacts must have the Approver flag. If nobody has it yet, tick it on someone first.
- Escalation level 1 is required for a new person. Once set it can be replaced but not cleared. Someone saved without one is at the top of the chain, shown as — (top of chain).
- Escalation level 2 is optional and must be a different person from level 1.
- Nobody can be their own escalation contact, and two people cannot be each other's L1.
- While someone is another person's escalation contact, their Approver flag cannot be removed. Give those people another contact first.
Teams
The Teams tab lists each team with its number of members. + Add team asks only for a Team name, and names must be unique. A team's members are the people whose Team is set to it.
Eight teams are master teams, marked Master: Marketing, F&D, Regulatory, Packaging, Quality, Operations, Finance and Management. Templates are built on them, so they cannot be renamed or deleted. Any team can be picked on a template activity, master or not.
Deleting any other team is refused while people are still on it, or while project or template activities use it, because projects and templates keep the team they were built with. People who were removed but still belong to the team show as +N removed; when the team is deleted they move to another team.
Editing a person
Edit opens the same form as + Add user, with everything editable. Changes to page access take effect on the person's menu and pages; tell them when you change their team or escalation contacts, because that changes who sees their alerts.
- A new email signs the person out. Their sign-in moves to the new Google account, and their current sessions end. The new address must be a company email that no one else uses.
- You cannot change your own email, or lower your own User Management access below Action; ask another admin.
Removing a person
The bin on a person's row removes them. Before anything changes, Srishti checks what they still hold.
- The PM of an open project cannot be removed. That includes a saved draft. Srishti shows <name> can't be deleted yet with the projects. Nothing in Srishti changes a project's PM today, so this lasts until those projects are closed, or until the PM deletes a draft they never submitted.
- Their escalation references are cleared. Anyone who has them as L1 or L2 is left with none and shows — (top of chain) until you pick someone else.
- Their unfinished activities are not reassigned. The confirmation names them; each project's PM gives them a new owner.
- Anything waiting on them as an approver gets stuck until a replacement approver is named. The confirmation lists those projects too.
- You cannot remove yourself.
| If the person… | What happens |
|---|---|
| Has never done anything in Srishti | They are deleted permanently, and the email can be used again. |
| Has history (almost anyone who has signed in) | User removed: they leave the list and can no longer sign in, but their history is kept. Adding the same email again asks Restore a removed user?; Restore account brings back that account with its history. |
Needs reassignment
When a removed person still owns open activities, each project's Overview shows a Needs reassignment card listing them: Assigned to <name> (no longer active), and Someone else is still assigned. when the activity has another owner too. The PM opens each activity and picks a new person under Assigned to. Finished activities are history and are not listed, and a closed project shows nothing.
For the steps, see Add and manage people and the Admin guide.