Who Should See What: Permissions for Office, Yard and Shop

Shared passwords and everyone-can-edit spreadsheets are convenient until something goes wrong. Here's a practical way to give each person the access their job needs.

Illustration of three access badges for office, yard and shop beside a shield

In many plants, access to information is all or nothing. Either everyone shares one password and can change anything, or information is locked in one person's computer and nobody else can see it. Neither works well. The first leads to accidental changes nobody can trace; the second creates bottlenecks.

The answer is a small, sensible set of permissions: everyone can see what they need, people can change only what their job requires, and every change is tied to a name. This article covers how to set that up for a truss plant's office, yard and shop.

Start with personal logins

The single most important step is to give each person their own login, rather than sharing one. Personal logins mean:

  • Every change has a name on it. When a delivery date moves or a count changes, you can see who did it.
  • Access can be removed for one person without changing everyone else's password.
  • Each person can have the right level of access instead of whatever the shared password allows.

Shared codes are often how plants start, and they're fine for getting going. But once more than a few people are involved, move to personal logins and then turn the shared codes off.

Three roles cover most plants

You don't need dozens of roles. For most truss plants, three levels cover nearly everyone:

RoleTypical peopleWhat they can do
AdminOwner, plant managerEverything, including managing people and logins, and bonus rules
EditorOffice staff, schedulers, yard leadUpdate jobs, inventory and builds: the day-to-day work
ViewerSales, estimators, supervisors who only need to lookSee the information, change nothing

Keep the number of admins small. Admins can add and remove people and change rules that affect pay, so those powers belong with the people accountable for them.

The shop floor is different

Crews building trusses need to do one thing with the system: record the work they're doing. They don't need to see costs, edit jobs or manage inventory. And they often work with gloves on, at a shared device, with no time to remember passwords.

For the shop floor, a better model is a dedicated link that does just that one job: start, pause and finish batches. No password, no access to anything else. Similarly, a shop TV should use a view-only link that shows the board and can't change anything.

Because these links work without a password, treat them like keys: share them only with the people and devices that need them, and replace them if they get out.

Match access to the job, not the person's seniority

A common mistake is giving access based on how senior or trusted someone is, rather than what their job requires. A long-serving yard lead may be completely trustworthy, but if they never need to change bonus rules, they don't need admin access. Least access isn't a judgement about a person; it's protection against accidents, compromised passwords and confusion.

Some practical guidelines:

  • Costs and pricing often only need to be seen by the office and management.
  • Bonus rules should be changed only by the people accountable for pay.
  • People and logins should be managed by one or two admins.
  • Job and inventory updates belong with the people who do that work.

Good access habits

Permissions aren't a one-time setup. A few habits keep them healthy:

  1. Turn people off promptly when they leave. Make it part of your leaving checklist. Turning someone off should sign them out everywhere.
  2. Review the people list regularly, for example every few months. Remove anyone who no longer needs access and check that roles still fit.
  3. Use strong, unique passwords, and never share them. If someone forgets a password, an admin should set a new one rather than everyone using a shared fallback.
  4. Watch for repeated failed sign-ins. Systems that lock a username for a while after repeated wrong passwords make guessing much harder.
  5. Be careful with connected apps. If someone connects an AI assistant or another tool to their account, it acts with their permissions. Make sure people know how to disconnect it, and that removing a person also disconnects their apps.

Where more detail helps

Three roles are a good start, but some plants eventually want finer control: an editor who can update jobs but not inventory, or a viewer who can't see costs. Those needs are real, and more detailed custom roles are a natural next step as a plant grows. Start simple, though. It's easier to add detail later than to untangle a complicated permission scheme nobody understands.

Summary

Give everyone a personal login, use a small set of roles (admin, editor, viewer), keep admin access with the people accountable for it, and give the shop floor simple single-purpose links instead of passwords. Turn people off promptly, review access regularly, and make sure connected apps are covered by the same rules.

Users & permissions in Truss Plant Portal work exactly this way: personal logins with admin, editor and viewer roles, a crew link and TV links that need no login, and every change signed with a name. More detailed custom roles are coming.

Tags: permissions logins roles security users