Give each person the systems their job uses
A company with a capture team, a proposal team, a contracts office and a finance department does not want every person in every system. Roles and access lets the owner say who opens what: a role for each kind of job, a system closed to one person beyond their role, and a history of every change.
printed on every notice, never searchable until now
Roles of your own, or four ready-made ones
Roles and access is under Administration in the menu. A role has a name, a base (member, viewer or manager), the systems it opens, and four permissions: change records, take files out, see pay, and add and remove people. An account keeps up to forty roles.
Four are ready to copy and change: Capture manager, Proposal manager, Contracts manager, and Finance and pricing. Each opens the systems that job uses. A copy is the account's own from the moment it is made.
- Open a whole part of the product, or single screens in it
- A role based on a viewer reads and changes nothing
- Only the owner gives a role that sees pay
- The owner can let managers edit roles and restrictions
every state the same size, so DC is readable
One person, closed beyond their role
The People tab lists everybody on the account with their role. For any one of them the owner can close more than the role does, so somebody brought in for one program does not see the rest. What is open to each person is shown part by part on one page.
The owner is never restricted. Everybody keeps Today, their own account, settings, watchlist, help, and Security, so nobody is ever locked out of their own sign-in.
- What is open to each person, on one page
- Who holds each role
- The History tab: every role made, changed or deleted, and every role given
a pipeline nobody updates is worse than none
Enforced on our servers
A closed system is closed on our servers, not only on the screen. Every request the app makes is checked against the role of the person making it, so an address typed by hand, a saved link or an export gets the same answer as the menu. A closed screen is not in the menu, the search or the shortcuts, and its address says who to ask.
Every change is a line in the account's history: who changed what, for whom, and when.
Your own menu
Apart from what the account allows, each person can hide the rows they do not use from their own menu. That is not a restriction. A hidden row is still reached by its address and by search, and Show hidden at the foot of the menu brings the rows back for a visit. It is on every plan, including One Code.
Where it stops
Roles and access comes with every paid plan. A role decides what a person opens in LastAwarded, not what they may do for your company: a role that opens Agreements does not make somebody your signing authority. A role cannot do more than its base allows, so a role based on a viewer never changes a record. One Code is one person, so it has no roles to give, and keeps the menu of your own.
Related
- Your teamSeats, the three bases, who sees pay and the Activity card.
- Security and privacy NewTwo-step sign-in, the lock screen and sessions.
- Messages NewA conversation on a record is read by those who may open it.
- PricingThe seats each plan covers.
- The platform NewWhere this sits among the eight parts of the product.
See who was last awarded in your NAICS
Every code, every buying office, every vendor and every recompete, organized from the federal record and read nightly. Open it with a plan.