Technology

Stone Fabrication Software Permissions Checklist

Test user roles, record visibility, and office coverage before choosing stone fabrication software. Includes an original demo policy and sign-off checklist.

Stone fabrication software permissions should be tested with real user roles before you commit to a system. Write down who may see each job, who may change it, and who may approve the next step. Then sign in as those users and test both the actions they need and the actions they should not have.

For a countertop shop, the practical question is simple: can an estimator work on assigned quotes while the office keeps the wider view it needs? A permission name alone does not answer that question. A short, controlled demo can show what each person can actually open.

Start With the Shop’s Access Rules

Before asking for a software demonstration, agree on a small access policy. Describe the work rather than starting with a vendor’s role names. One company’s “sales” role may cover different responsibilities from another’s.

Separate four decisions: viewing information, changing information, approving a decision, and taking information out of the system. A user who can read a quote does not necessarily need to change its price. A user who needs a project address may not need every other project in the office.

Write requirements as questions until the vendor has demonstrated them. Do not assume a system supports a particular restriction because its brochure mentions permissions.

  • Which records should each role see: its own, an assigned group’s, or all records?

  • Which fields or documents must each role change to finish its work?

  • Who is responsible for approval before the shop acts on a quote or change?

  • What should happen when the usual owner is away or leaves the company?

  • Which download, print, sharing, or export actions need a separate check?

For the wider evaluation, use the ERP and shop management overview. This checklist deals specifically with access, rather than the whole buying decision.

Original Example: A Small Shop’s Demo Policy

The following is an original planning example, not a Stonify preset or an industry standard. Adapt it to your shop and ask the vendor to confirm which requirements the product can enforce.

  • Estimator: prepare assigned customer quotes; ask whether other estimators’ records can be hidden when that is the shop’s policy.

  • Office manager: locate every active quote and project, cover an absent colleague, and inspect which roles grant access.

  • Field user: open the job information needed for the day; ask what mobile access includes and whether it follows the same visibility rules.

  • System administrator: manage users and roles; demonstrate the process for removing access when someone leaves.

Keep business approval separate from software access. If the office requires a manager to approve an unusual discount, ask whether the software enforces that rule, merely records it, or needs a separate procedure. Record the answer instead of assuming that an approval workflow exists.

Build Two Fictional Jobs for the Test

Use invented customer details and clearly labeled demo records. Create one quote or project assigned to the test estimator and another assigned to someone else. Ask the demonstrator to explain any sample-data limitations before starting.

Sign in through the normal account for each role. An administrator clicking around a settings screen can explain configuration, but it does not prove what the estimator sees after signing in.

For each requirement, record the role, record ownership, action attempted, expected outcome, actual outcome, and follow-up. “Could open the assigned quote” is useful evidence. “Permissions looked good” is too vague to guide a buying decision.

Test Allowed Work and Unwanted Access

Start with an ordinary task: find the assigned customer, open the quote, make an allowed change, and return to the work list. Then try to open the second test record through the normal navigation.

Repeat the relevant checks using another route, such as a saved record link or search, if the system provides one. A filtered list and a restriction on opening a record answer different questions. Ask the vendor to explain any difference you observe.

Next, test the actions that matter to your shop: editing an amount, changing an owner, opening a document, or downloading information. These are evaluation questions, not claims that every product has a separate permission for each action.

If the required control is unavailable, write down the proposed workaround and who would own it. The buyer needs to know whether that workaround is acceptable before the contract or migration decision.

Check Coverage and Role Changes

Access rules also need to work when someone is out of the office. Ask the manager to cover the estimator’s test job using the intended everyday process. Record whether coverage requires reassignment, a different role, or another procedure.

Then change the test user’s role and repeat the important checks. Ask whether the user must sign out, refresh, or take another step before the change applies. Test on the devices the team will use if mobile work is part of the purchase.

Make these checks part of the software migration checklist. Roles should be checked before the first live jobs depend on them.

What Stonify Has Documented

Stonify’s November 17, 2026 release notes describe configurable sales visibility. The published example lets salespeople open their own quotes, projects, and leads while the office sees everything. The settings are available through Sales visibility in User management or the Visibility tab in the Leads, Quotes, and Projects settings.

The same release says the Users list shows what each person can open. Earlier September 22 release notes describe inspecting a user’s permissions and the roles granting them, plus a View by Permission view.

That makes Stonify a concrete option to evaluate when your shop wants own-record sales access alongside an office-wide view. Ask to see those documented controls using your role policy. Requirements such as price-change restrictions, approval enforcement, or export limits still need their own demonstration; these release notes do not establish all of them.

Keep a Usable Sign-Off Checklist

Before approving the purchase or rollout, keep this completed record with the evaluation notes:

  • Each everyday role has a named business owner.

  • Required viewing and editing tasks have been demonstrated through that role’s account.

  • At least one record outside the role’s intended scope has been tested.

  • Absence coverage and a role change have been checked.

  • Mobile, document, sharing, and export requirements have specific answers where relevant.

  • Unavailable controls and workarounds are written down.

  • The shop owner or responsible manager has accepted the remaining gaps.

If data access is part of the decision, pair this with the software data export checklist. Being able to work in the system and being able to take business records out are separate evaluation steps.

Bring your role list and two fictional job examples to a Stonify demo. Ask the team to demonstrate own-record visibility, office coverage, and permission inspection against that list, then document any requirements that need further confirmation.

Ready to Run a Smarter Stone Operation?

Book a demo to see how Stonify can reduce costs at your shop.

Ready to Run a Smarter Stone Operation?

Book a demo to see how Stonify can reduce costs at your shop.