Skip to main content

Company Settings Overview

Where an Admin sets up users, roles and permissions, cost codes, order rules and company-wide defaults for everyone at your company.

Written by Gabby Gutman

Company Settings is where an Admin sets the rules everyone else works inside: who has an account, what each role can do, and the defaults that apply to every project and order.

Before you start

  • You need the Admin role to change anything here. Purchasers can open it and read it, but the only thing they can change is Addresses.

  • Users, Material Requesters and AP Users have no entry for it at all.

  • Company Settings is the default name. Your company can rename it.

How to open it

Click your name in the top navigation bar, then Company Settings.

What is on each tab

There are up to 11 tabs across the top:

  • Users: everyone with an account. Invite people, change a role, deactivate, re-activate or replace someone.

  • Project Groups: which projects each person can see. This is the default name and your company may have renamed it.

  • Permissions: what each role can do. Only Admins see this tab.

  • Addresses: your saved delivery and billing addresses.

  • Cost Codes: whether cost codes carry a class and a phase code, and whether they are specific to a project.

  • Orders: required fields, defaults and email settings for orders and RFQs (requests for quote).

  • Invoices: how invoices move through review and approval.

  • Commitments: settings for commitments.

  • Project Management: settings for concrete batch tracking.

  • Other Settings: company-wide switches, branding, notifications and terms.

  • Downloads: file exports for your accounting system.

You may see fewer than 11. Cost Codes, Invoices, Commitments and Project Management appear only if your company uses them, and Permissions appears only for Admins.

Notes and limits

  • Each tab saves on its own. There is no single save for the whole area.

  • Changes here apply to everyone at your company, across every project, as soon as you save.

  • SubBase does not keep a history of settings changes, so there is no list of what changed or who changed it.

Best practices

  • Set up Project Groups before you invite anyone. Once 1 group exists, every invitation has to include at least 1 group, so inviting first means going back to fix access afterwards.

  • Change someone's role in the Role column on the Users tab. Deactivating them and sending a fresh invitation leaves 2 records for 1 person, and the orders stay on the old one.

  • Save before you move between tabs. Save Changes on Other Settings does not save Permissions, and only Permissions warns you before you leave.

If this doesn't work

Start a chat from the Messenger in the bottom-left of this page, or email help@subbase.io. Include the order or project number and what you expected to happen.

Related

Did this answer your question?