Workflows
Add and manage people
Add a person to Srishti, give them a team, page access, approver authority and escalation managers, change any of it later, and remove them when they leave.
- Admin
Everyone who uses Srishti is set up in User Management. What you enter there decides which pages a person can open, which activities they can be given, whether they can approve, and who hears about it when their work runs late.
This page walks through adding a person, changing them, removing them and keeping the team list tidy.
Before you start
- Who does this: anyone with User Management: Action in their page access. With View you can see the lists, but you cannot add, change or remove anyone.
- What you need: the person's name, their @kapiva.in Google address (they sign in with Google, so there is no password), the team they work in, and what they need to open.
- Check the team exists first. Open the Teams tab. If the team is missing, add it there before you add the person.
- Have an approver ready for escalation. Every new person needs an escalation level 1, and only people marked as approvers can be picked for it.
Switch between the people list and the team list.
Find a person, or narrow the list with All teams and All project types.
Opens the Add user form.
One pill per module the person can open, with View or Action. Modules set to None are left out.
Who hears about this person's late work. — (top of chain) means nobody is set.
The pencil opens the Edit user form. The bin beside it (Delete user) removes the person. Your own row has neither.
Add a person
- Open User Management. Stay on the Users tab and choose + Add user.
- Enter the name and email. Email ID is the Google account they sign in with. Only a company address is accepted.
- Pick the team. The Team list shows the eight master teams first, then any other teams. The team matters: an activity's owner can only be picked from that activity's team.
- Set page access. For each module choose None, View or Action. Every module starts at None except My Activities, which is always Action. Give the least the person needs.
- Tick the approver box if they decide approvals. Under Approver, tick This person is an approver for anyone who approves new projects, baselines or activities.
- Choose the escalation managers. Escalation level 1 is required. Escalation level 2 is optional and must be a different person. Both lists offer only active approvers, shown as email — name.
- Optionally tag project types. Project types only label the person for filtering the list. They do not open any project to them.
- Choose Add user. The button stays off until name, a valid email, team and escalation level 1 are filled. The list reloads and shows the new person.
| Module | Levels | What Action adds |
|---|---|---|
| Portfolio | None, View | No Action level. View opens the Portfolio page. |
| Projects | None, View, Action | Create projects and act on pending approval submissions. |
| Templates | None, View, Action | Create templates and edit the ones you created. |
| User Management | None, View, Action | Add, edit and remove people. |
My Activities is not in the grid. It is the home page and is Action for everyone, so there is nothing to choose.
For what each level opens, see Page access: what you can open.
Change a person's details
The name shown everywhere in Srishti.
Their Google sign-in. Changing it moves their sign-in to the new address and signs them out.
Decides which activities they can be made owner of.
Click a level to change it. My Activities stays on Action.
- Find the person. Search by name or email, then choose the pencil (Edit user) on their row.
- Change what you need. Name, email, team, page access, project types, the approver box and the escalation levels can all be changed here.
- Choose Save changes. Page access and approver authority are checked on every request, so the change applies the next time the person opens a page.
Rules when editing
- A new email signs the person out. Their live sessions end, and they sign in again with the new Google account. The address must not belong to anyone else, including a removed person.
- Escalation level 1 can be replaced but not cleared. A person who has no level 1 today (top of chain) can be saved without one.
- A person can't escalate to themselves, and two people can't be each other's level 1.
- The approver box stays ticked while someone escalates to this person. Give those people another approver first, then untick it.
- You can't edit or delete yourself. Your own row has no Edit or Delete, and Srishti refuses the change if it is sent any other way (You cannot edit your own account here). Ask another admin.
Remove a person
- Choose the bin on their row. Srishti first checks what the person still holds.
- If they run a project, stop. A window saying they can't be deleted yet lists the projects they are PM of. Removal is refused while they are PM of any project that is not closed or cancelled, including a saved draft.
- Read the confirmation. It says what removing them changes: who loses them as an escalation contact, which unfinished activities they still own, and any approvals that will be left waiting on them.
- Choose Delete. Someone with no activity in Srishti yet is deleted permanently, and their email can be used again. Anyone else is kept for the record: they leave the list and can no longer sign in, and a User removed window lists the open activities that need a new owner.
Bring someone back
To restore a removed person, add them again with the same email. Srishti asks Restore a removed user?; choose Restore account. The same account comes back with its history and any work still assigned to it, and the name, team, access and escalation are taken from the form.
Manage teams
- Open the Teams tab. Each team shows how many people are on it.
- Add a team. Choose + Add team, enter a Team name and choose Add team. Names must be unique.
- Rename or delete a team you added. Use the pencil or the bin. The eight master teams show Locked: templates are built on them, so they can't be renamed or deleted.
Delete is unavailable while anyone is still on the team, or while a project activity, template activity or document route uses it. Hover the bin to see why.
What happens next
A new person signs in with Google and lands on My Activities. Their menu shows only the modules you gave them View or Action on.
Their escalation managers hear about their late work. A daily check at 6:00 AM IST looks at activities on running projects:
| When | Who is told |
|---|---|
| 2 days before the due date | The activity's owner (Due in 2 days). |
| On the due date | The owner's escalation level 1 (Due today). |
| 4 days after the due date | The owner's escalation level 2; with no level 2, level 1's own level 1 (Overdue by 4 days). |
| An activity approval waiting over 24 hours | The approver's escalation level 1, once a day, up to 3 times. |
When you remove someone, their open activities stay with them until the project's PM picks a new owner. They show under Needs reassignment on each project's Overview. See Unblock a stuck project.
What can go wrong
| Problem | Why | What to do |
|---|---|---|
| Add user stays greyed out | Name, a valid email, team or escalation level 1 is missing. | Fill in every field marked with a star. |
| The escalation lists are empty | Escalation contacts must be approvers, and nobody is one yet. | Edit a suitable person and tick This person is an approver first. |
| "Use a company email" | The address is not a company Google account, so it could never sign in. | Use their @kapiva.in address. |
| "A user with this email already exists" | Someone active already has that address. | Search for them and edit that row instead. |
| The person can't be picked as an activity owner | Owners come from the activity's team, and only active people are offered. | Check their Team here. |
| Late-work alerts reach nobody | The owner's row shows — (top of chain). | Edit them and set Escalation level 1. |
| "You cannot delete your own account" | Nobody can remove themselves. | Ask another admin. |