Guides by role
Admin guide
Admins set Srishti up for everyone else: add people to the right teams, give each person the right page access, keep the activity templates and document folders in good shape, and step in when a project or an alert chain gets stuck.
- Main page ·
/admin/org
Your main page
On this screen
Click a number on the screen, or an item in this list, to see that part up close.Tap an item in this list to see that part up close.
What you will see
- Everyone signs in to My Activities. The left menu shows only the modules your page access allows — an Admin usually sees User Management and the template pages on top of the everyday ones.
- User Management lists your Users and Teams. The user list can be searched and filtered by team and by project type.
- Each user shows their team, their page-access pills (modules set to None are left out), their project types and their escalation managers. Open Edit to see or change whether they are an approver.
- Portfolio gives a read-only view of every active project's health, so you can see where people may need help without opening each project. Completed and closed projects are on Projects.
First things to do
- Open User Management and check that every team you work with exists before adding people.
- Add each person with their name, email, team and page access. Give Projects Action only to people who create projects, and User Management Action only to other admins.
- Set an escalation manager (L1) for every person who owns activities. Without one, due-today and overdue alerts for that person have nobody to go to.
Pages you will use
| Page | What it is for | Address |
|---|---|---|
| User Management | Users, teams, page access, escalation managers and approver flags. | /admin/org |
| Activity Templates | Create, edit, publish and duplicate the templates that new projects start from. | /templates |
| Document Storage | Folder structures that organise project documents. | /doc-storage |
| Portfolio | Read-only health view of every active project. | /portfolio |
Add or change a person
/admin/org
Page access decides which pages a person can open, and whether they can change things there. Change it here and the person's menu and reachable pages change with it. What they see inside a project still depends on their part in it: the activities assigned to them, the projects they run and the approvals addressed to them.
- Open User Management → Users, then choose Add user (or open an existing person to edit).
- Fill in name, email and team, and set the escalation manager (L1, and L2 if you use one).
- Set the five page-access levels. Dashboard is View at most. My Activities is always Action — it is everyone's home page and cannot be changed.
- Switch Approver on for people who will approve baselines and activities. Project types on a person are only a label for filtering the user list; they do not give access to any project.
- To remove someone, choose Delete on their row: Srishti first lists what they still hold. You cannot delete the PM of an open project or a saved draft. Their unfinished activities are not reassigned automatically — each project's PM gives them a new owner. Someone with no history is deleted; anyone else is kept for the record, and adding their email again offers to restore them.
Keep the templates ready
/templates
Activity templates are what every new project starts from. Each project gets its own copy once, so editing a template later never changes a running project.
- Open Activity Templates and check each template's type, activities, durations and dependencies.
- Create a template, or edit one you created. A new template is a Draft: choose Publish template once every activity without sub-activities has a team and at least one task, and the first activity has no predecessor. Only published templates can be picked for a new project.
- You can keep editing a template you published; the changes reach only projects created afterwards. Templates created by other people can be duplicated, but not edited.
- Open Document Storage to keep the folder structures documents are filed under. Publish a structure before you pick it on an activity template — it can be published once every folder has a document. While a template uses it, you can add folders and documents but not rename or delete them.
- Pick the right document storage before you publish an activity template: a published template keeps it. To use a different one, duplicate the template.
Find out why a project or an alert is stuck
/portfolio
Most 'it is not working' reports are a setup issue — a wrong team, missing access or a missing escalation manager — not a project issue.
- Use Portfolio to spot the project: filter by status, then open it for the detail.
- If someone cannot see a page or an activity, check their page access and team in User Management first.
- If alerts are not reaching the right person, check that the owner has an escalation manager set.
Guardrails
- Page access decides which pages a person can open. Give each person the least they need — View when they only need to look, Action when they must change things.
- Only an activity template's creator can edit or publish it. Duplicate someone else's to adapt it. Document storage structures can be edited by anyone with Templates: Action.
- Do not use Portfolio to change anything. Open the project to act on it.
When to hand the work off
- Send project questions — dates, activities, baselines — to the project's PM.
- Send approval questions to the approvers named on the project.
- When you change someone's team or manager, tell them: it changes who sees their alerts.