How to decide who needs a full PSA license and who can use restricted access

Give a full PSA license to anyone who changes project plans, budgets, staffing, or approvals, or who runs financial and resource reports. Give a restricted seat to people who mostly enter time, update assigned tasks, view status, or approve a defined item. Ask one question per person: do they change the plan, or only report against it?

Job titles rarely settle this. A project manager may need broad rights, while a senior specialist may need task-level access only. Match each seat to what the person does every week, so the firm pays for control only where control is used.

What do full and restricted PSA access mean?

A full PSA license gives a person the rights to manage or control a material part of delivery: creating projects, changing schedules, assigning people, approving time, reviewing budgets, or running management reports. Restricted access covers a narrower slice. A team member logs time and updates assigned tasks, a client approves a deliverable, an executive reads a dashboard. None of them changes the wider project record.

Labels vary by vendor. One product’s collaborator can log time and update tasks, another’s can only comment. A guest category may be included in one plan and billed in another. The permission set matters more than the label.

How Birdview defines its license types

Birdview’s Enterprise plan has four license types, compared permission by permission on its pricing page [2]. The Team plan is priced per user and includes up to 20 free guest users. Role-based tiered pricing is part of the Enterprise plan.

Birdview’s own guidance describes collaborators as team members who log time and update tasks (see the business case for PSA software), and guests as unable to track time [3].

Two Birdview features support this split. Job Roles describe what someone does: their skills and billing rates. Access Levels control what they can see and change. Keeping the two separate lets a senior specialist keep a senior job role without receiving project-manager permissions. Details are in the Birdview Knowledge Base [4].

What should you ask before assigning a seat?

Five questions settle most seats. Use the answers instead of total headcount.

1. What data must the person see?
2. What records must the person edit?
3. Can the person approve time, scope, budget, invoices, or change requests?
4. Does the person need reports, resource plans, or financial information?
5. Who is accountable if that record is wrong?

This is the principle of least privilege: each user gets only the access needed to do the job [1]. It limits exposure of sensitive project and financial data, and it keeps the license bill honest.

Which roles need a full license?

A role-to-license matrix stops a small firm from buying one tier for everyone. People in small firms wear two hats, so the same person may do delivery work on Monday and approve budgets on Friday.

Working on a project does not automatically justify a full license. Broad access is right when a person controls the project record, changes commitments, or acts on sensitive reports.

What separates a full seat from a restricted one?

A person needs a full license when their work requires broad data visibility, project editing, approval authority, resource decisions, or operational reporting. A restricted seat fits people who complete defined actions without controlling the wider project record.

The difference matters because project edits change delivery commitments. A time entry records completed work. A schedule change can alter staffing, client expectations, billing timing, and forecasts. Both happen inside a project, but they carry different consequences.

How should you handle mixed roles?

Small firms often combine responsibilities. A consultant may lead one engagement, contribute to three others, and approve subcontractor hours on a fourth. Give that person the rights of their highest-risk recurring responsibility. A recurring project-lead role usually needs a full license. A rare approval task should use temporary elevated access where the platform allows it, removed once the responsibility ends.

System rights should follow decision authority, not seniority. A senior adviser who reviews deliverables may only need a read-oriented seat. A junior coordinator who changes schedules across active projects may need a full license.

When does restricted access start to block work?

Restricted access has failed when people regularly ask someone else to make ordinary changes. Other warning signs are shadow spreadsheets and project updates sent by email because the system rejects the input. A restricted seat should support work that happens every week. A manager can handle occasional exceptions, but once exceptions become routine, the firm has misclassified the role.

How many of each license do you need?

Count people who need full rights each month, then regular restricted users. Keep clients, contractors, and temporary staff in separate groups. This gives a clearer purchasing picture than one employee total.

1. List roles before listing employees.
2. Record the actions each role must complete in the PSA.
3. Assign the minimum permission set that allows those actions.
4. Count permanent full users, then regular restricted users.
5. Count clients, contractors, and temporary staff separately.
6. Re-count when staffing, service lines, or responsibilities change.

For scale, Birdview’s requirements checklist notes that a typical professional services firm runs 20 to 60 full users alongside 50 to 200 collaborators or guests, and that paying full-user rates for light users is the most common overspend.

Avoid shared accounts. They make audit trails unreliable, hide who approved or changed a record, and may breach vendor terms. A shared login resembles a shared signature on a contract: convenient until someone asks who actually signed. Review rights quarterly, and sooner when a role changes.

What does it cost, and how do you avoid over-licensing?

Cost depends on full seats, restricted seats, external-user rules, plan tier, and contract minimums. Counting roles instead of employees often changes the total sharply.

On Birdview’s Team plan, every paid seat costs the same: currently $37 per user per month billed annually (shown as a special offer against a $41 list price), for 5 to 100 users, with up to 20 free guest users [2]. Each client or reviewer who can work as a guest instead of a paid seat saves about $444 a year at that rate. Enterprise adds role-based tiered pricing and a guest allowance of 20 users or 15% of full licenses, whichever is higher, with Enterprise pricing quoted individually. Prices change, so confirm current figures before budgeting.

Also count the time spent assigning, reviewing, and removing access. A cheap restricted seat can cost more over time if administrators repeatedly do work the user cannot.

What are the signs of over-licensing?

• A full-license user only enters time and reads saved dashboards for most of the review period.
• A full-license user has not edited projects, approved work, or used management reports for months.
• A contractor keeps rights after the assignment ends.
• A client holds a paid internal-style seat but only uses milestone approvals.

What are the signs that access is too narrow?

• Project managers ask administrators to change schedules or assignments.
• Delivery staff cannot enter required time or update assigned work.
• Finance staff export data because they cannot see records needed for billing.
• Contractors cannot submit files without sending them to an employee.

A seat review should end in one of four actions: retain, downgrade, upgrade, or remove. Keep a dated record, which helps at renewal. For contract-level protections such as the right to mix full and limited licenses and to reduce seats mid-term, see our guide to PSA contract terms.

How should clients and contractors get access?

Clients and contractors rarely need internal project-manager rights. Start with a guest or restricted external seat, and add access only when a defined task requires it.

On Birdview, guest users sign in through a dedicated Guest Portal. They can add issues and requests, view their own issues and requests, view project progress and details, upload and download files for their projects, and use the message board. They cannot track time, create tasks, or open activities that were not assigned to them [2][3]. See Birdview’s guide to guest users and the client portal page for details.

A contractor who must log time cannot be a guest, which is why the time-entry question belongs on the checklist. Why give a contractor a full license to view a deadline and upload a file? Usually there is no good answer.

External access should end when the business purpose ends: when the contract or statement of work closes, a contractor’s assignment finishes, a client contact changes employer, or the project is archived.

Do plan tiers change who needs which license?

Sometimes. Plan scope and user rights are separate decisions, but a feature gated to a higher plan can change who needs access. On Birdview, resource planning (Allocations), expense approval, single sign-on, and user audit reports are Enterprise features [2]. A firm that needs them should choose the plan first, then count seats by role. Buying a module does not mean every employee needs a full license for it.

Before signing with any vendor, ask for a trial demonstration of each workflow with a project manager, a delivery team member, a client, and a contractor, and get permission limits in writing. A feature list cannot replace a permission matrix. For help choosing a platform, see the mid-market PSA buyer’s guide.

FAQ

How should a services firm decide who needs a full PSA license versus a restricted seat?

Give a full license to people who manage projects, approve work, plan resources, handle financial records, or make decisions from PSA reports. Use restricted seats for people who log time, update assigned tasks, upload files, view status, or approve a defined item. Decide by what the person changes each week, not by job title.

How should a firm size license tiers across project managers, team members, and occasional contributors?

Count recurring responsibilities, not headcount. Project managers and operational decision-makers usually need full licenses, regular delivery staff usually need restricted seats, and occasional contributors, clients, and contractors should be counted separately because their involvement is temporary or external. Re-count whenever roles or service lines change.

How do full, collaborator, and guest seats affect PSA rollout cost?

Full licenses drive most of the subscription cost because they carry the broadest rights. On Birdview’s Team plan every paid seat is currently $37 per user per month billed annually, and up to 20 guest users are free, so moving clients and reviewers to guest access reduces paid seats. Check current pricing before budgeting.

What is the most cost-effective way to give clients and contractors access without full licenses?

Use guest access for clients and for contractors who only view assigned work and upload files. Contractors who must log time need a restricted paid seat, because guests cannot track time on Birdview. Keep internal financial, staffing, and portfolio data out of external accounts by default.

Should finance staff always receive a full PSA license?

No. Finance staff need a full license when they manage rate cards, expenses, other people’s time entries, or billing in the platform. A read-oriented seat can work when they only review financial information and reports. Check the exact permissions behind each license label before deciding.

Can occasional contributors share one PSA account?

No. Shared accounts weaken audit trails, hide who approved or changed a record, and may breach vendor terms. Give each person a named restricted seat or, for clients and external reviewers, a guest account where the vendor supports it.