Getting started
Page access: what you can open
How Srishti decides what each person can open and change: five modules set to None, View or Action (Portfolio only None or View, My Activities always Action), the separate Approver flag, and the PM of each project.
- Everyone
What you can open in Srishti is set for you personally, not by a job title. Each person has a page-access grid: five modules, each set to None, View or Action (Portfolio offers only None and View, and My Activities is always Action). The left menu, the pages you can reach and the buttons you can use all follow that grid, and the server checks it on every request.
Two things sit outside the grid. The Approver flag decides who can approve, and inside a project its PM has the right to change the plan. This page explains all three.
How page access works
There are no roles such as "PM" or "Viewer" that bundle permissions together. An admin sets each module for each person, so someone can, for example, view projects and edit templates without being able to manage users.
- None
- The module is not in your menu and its pages are closed to you.
- View
- You can open the module's pages and read everything on them.
- Action
- You can also create and change things there.
A new person starts with every module set to None except My Activities, which is always Action for everyone: it is the home page. Portfolio has only None and View, because there is nothing to change on it.
To see your own grid, click your name at the bottom of the left menu and choose View profile. The Page access card lists each module with your level.
What each level allows
| Module | None | View | Action |
|---|---|---|---|
| Portfolio | No Portfolio page | Open Portfolio, read-only | Not offered |
| Projects | No Projects page; you reach your work through My Activities | The project list and every project's page, read-only | Also + New project: create projects, which you then run as their PM |
| Templates | No Activity Templates or Document Storage | Browse templates and document storage structures, read-only | Create templates, edit and publish your own, duplicate anyone's, and edit document storage |
| User Management | No User Management page | See the people and team lists | Add, edit and remove people and teams, including their page access |
| My Activities | Not possible | Not possible | Always: your activities, tasks, documents and conversations, and Approvals & Alerts |
Portfolio shows the same projects as Projects would. With Projects: View or Action that is every project. With Projects: None it is only the projects you are PM of, so Portfolio: View is most useful together with Projects: View.
Action on Projects does not let you change other people's projects. Only a project's own PM changes its plan; see The PM of a project. Likewise, Action on Templates lets you edit only templates you created yourself.
The Approver flag
Approving is not a page level. It is a separate checkbox on each person in User Management: This person is an approver. A person with the flag can:
- be named as one of a new project's one to three baseline approvers, who decide a plan that runs over its template and every new baseline;
- decide activity approvals addressed to them;
- be chosen as someone's escalation contact (Escalation level 1 or 2).
Being an approver does not open any page by itself. An approver who only needs to decide works from Approvals & Alerts, which everyone has. Being able to open a project does not make you its approver either: you decide only what is addressed to you.
The flag cannot be removed from someone while other people escalate to them; give those people another escalation contact first. The Project types on a person are only a label for filtering the user list; they give no access to any project.
The PM of a project
Inside a project, one more rule applies. The person who creates a project is its PM, and stays its PM: nothing in Srishti can change a project's PM today. The PM's name is in the project header.
Only the PM sees the project's Actions menu (Create new baseline, Close project) and the controls that change a running plan: + Add activity, the Edit activity section of an activity, Mark as done and Delete. Everyone else who can open the project sees the same page without them.
Activity owners do not need Projects access to do their work. Each owner finds their activities and tasks in My Activities, and the PM can complete tasks on any activity of their project too.
When you don't have access
- The menu leaves the page out. Modules set to None are not shown at all.
- Links take you elsewhere. If you open a link to a page your grid does not include, Srishti takes you to a page you can open, usually My Activities.
- Changes are refused. If you can view a page but not act on it, the server refuses any change, even one sent another way.
- Things you are not part of stay hidden. You only see projects, activities and documents your access and your part in the project allow.
Who can change access
People with User Management: Action add and edit people, so they set everyone's page access, Approver flag, team and escalation managers.
The person's name as it appears across Srishti.
Their Google sign-in. Changing it moves their sign-in to the new address and signs them out.
Their team decides which activities they can own.
One control for each module in the grid. My Activities is not in the grid: it is always Action. Portfolio offers only None and View.
- Open User Management. Stay on the Users tab.
- Find the person. Search by name or email, then choose Edit on their row.
- Set each module. Pick None, View or Action under Page access. Tick or clear the Approver checkbox below it if needed.
- Save. Choose Save changes. The person's menu changes the next time they open a page.