Understand Your Customization Rubric
Changelog: v2 reframes the rubric as the formal surface for permission and Moola changes based on Dan's clarification: the rubric is not just a tabular description of role configuration, it is the document support uses to coordinate change requests. Includes the Instructions, Permissions, Moola, and Support tabs. v1 framed the rubric only as an organizational tool; this version captures its actual operational role.
At a glance
A customization rubric is the Google Sheets document your store uses to formally request permission changes and Moola changes. It captures your store's full role and permission configuration, and it is the surface support and the OneClick team work from when implementing changes. This reference explains what is on each tab, the three-step change process, and how to use the rubric well.
Before you start
This is a reference article. Read it once, return when needed.
Core reference content
What the rubric is and why it exists
The customization rubric is a Google Sheets document tailored to your store. Every store using OneClick is given access to its own rubric. It captures the current permission and Moola configuration for your store, and it is the formal surface for proposing and tracking changes to either configuration.
The rubric exists for a few interrelated reasons. First, changes to permissions and Moola often have wide blast radius. A single permission name (for example, Manage Checklists) can apply to several roles, and a change to one row of the rubric may affect many team members. Routing changes through a structured document keeps everyone aligned on what is changing before it is changed. Second, support needs a paper trail. When OneClick or support implements a change, the rubric is the audit log. Third, leaders inside the store need to coordinate. Permission changes typically require sign-off from a leader who carries the Edit permissions capability. The rubric is the place where those leaders see the proposed state before approving.
The rubric is intentionally external to the OneClick product. There is no in-app rubric editor. Keeping the rubric in Google Sheets means it can be reviewed, shared, and audited without anyone needing OneClick access.
What is on the rubric
A customization rubric has four tabs.
Instructions. A static tab explaining what the rubric is for, how to propose a change, and what support does once a change is submitted. New leaders should read the Instructions tab before touching any of the others.
Permissions. The tabular layout of every OneClick permission against every role at your store. Each row is a permission. Each column is a role. Each cell is a checkbox or similar marker showing whether the role has the permission. A Notes column at the right captures store-specific reasoning ("we restricted Manage Checklists to Manager and above because we had drift across stores"). This is the most-used tab.
Moola. The Moola earning, redemption, and budget rules for your store. Captures who earns Moola for what behaviors, who can redeem (and at what amounts), how spending budgets are set across leaders, and any Moola Store catalog details that diverge from defaults. Some stores have minimal Moola configuration; some have extensive rules.
Support. A workspace tab for proposing changes. When you want to change a permission or a Moola rule, you note the change here. Support sees the proposed change, applies it, and the Support tab is the record of what was requested and when.
The three-step change process
Permission changes and Moola changes both flow through the rubric. The process is the same for both:
- Propose the change in the Support tab. Note the row (permission name or Moola rule) and the proposed new state (which role gains or loses the permission, what the new Moola amount is, and so on). Sign with your name and date.
- A leader who carries the Edit permissions capability reviews and signs off. This is typically a Director-tier leader, but the role is configurable. Sign-off can be inline in the Support tab or via a side channel; either way, support waits for it before applying.
- Support applies the change. OneClick's support team reads the Support tab, makes the corresponding edit to the live permission or Moola configuration, and updates the Permissions or Moola tab to reflect the new state. The Support tab line stays as a record.
The Support tab is intentionally a workspace, not a perfect record. The Permissions and Moola tabs are the source of truth for current state; the Support tab is the change log.
Who can edit the rubric
The rubric is shared with your store's leaders, not the entire team. Typical access:
- Director-tier leaders. Edit access to all four tabs.
- Manager-tier leaders. Edit access to the Support tab. Read access to the others.
- Below Manager. No access by default. Some stores share read access to the Permissions tab broadly so team members can see their own role configuration.
The exact access pattern is up to your store. The rubric is a Google Sheets document; sharing follows Google's normal sharing model.
How permission requests cite the rubric
When a Permission Change request goes to support, it should reference the rubric row. A good request reads something like: "Per row 12 of the Permissions tab, please move Manage Checklists from Manager to Shift Leader. Sign-off recorded by [Director name] on [date]." This is much faster for support to act on than free-form text, because the row reference disambiguates the change immediately.
The same pattern applies to Moola changes. "Per row 5 of the Moola tab, please increase the per-shift earning for the Speed of Service Star from 5 to 10 Moola." Cite the row, propose the new state, record sign-off.
What the rubric is not
The rubric is not the OneClick product. The product reads from its own permission and Moola configuration database. The rubric is the human-readable mirror used for change management.
The rubric is not a substitute for the Permissions module. Roles, permissions, and the rubric are three different things. The role is what the team member is set to in OneClick. The permission is the underlying capability the role unlocks. The rubric is the document that describes the role-to-permission mapping for your store. Changing a role does not change the rubric, and changing the rubric does not change a role; the rubric is updated to reflect role changes after the change is applied.
The rubric is not required to use OneClick. A store can run permissions and Moola entirely through ad-hoc support requests. The rubric is the structured option that scales to multi-store organizations and to stores that change role configuration frequently.
When to ask for a rubric
If your store does not have a customization rubric, ask your operator or your OneClick contact. New stores onboarded onto OneClick are typically given one as part of setup; older stores sometimes operate without one.
If your store has a rubric but you do not have access, ask your store's Director or whoever configures roles. Access is granted store by store, leader by leader.
Video
Not planned.
Common gotchas
I edited the Permissions tab directly and the change did not happen in OneClick. Editing the rubric does not change OneClick. The Permissions tab is a mirror; only support can change the live configuration. Move the proposed edit to the Support tab and follow the three-step process.
A change was applied in OneClick but the Permissions tab is out of date. This happens when changes go through ad-hoc support requests instead of the rubric. Reach out to support and ask them to reconcile the Permissions tab against the current live state. Going forward, route all changes through the Support tab to keep the mirror accurate.
The Notes column on the Permissions tab has stale or contradictory entries. The Notes column is for store-specific reasoning, but it is not auto-maintained. If you see something contradictory, flag it to your store's Director and ask for an audit pass.
I do not see a Moola tab on my rubric. Some stores have Moola disabled or have a minimal configuration that did not warrant a separate tab. If you want to start using Moola or expand the configuration, contact support and ask them to add the Moola tab and seed it with current state.
I want to give one team member a one-off permission and the rubric does not have a way to do that. Correct. Permissions flow through roles, not individual team members. The rubric is row-by-permission and column-by-role; there is no row-by-team-member surface because permissions are not assigned that way. Either assign a role that carries the permission or request a role configuration change.
The Support tab is huge and I cannot find the change I submitted. Use ctrl-F or cmd-F to search for your name or date. The Support tab grows over time and is not aggressively pruned because it functions as the change log. Old entries are intentionally kept.
Related articles
- Understand Permission Levels (Reference)
- Request a Permission Change (How-To Guides)
- Why a Permission Change Has Not Taken Effect (Troubleshooting)
Still stuck
If the rubric is missing, out of date, or producing confusing results, contact support at OneClickApp.com/support. Reference your store and what tab is in question. If a permission or Moola change is urgent, note the urgency and the business impact in the Support tab and ping support directly so they see the row.
Pre-publish checklist status
39 ad3da1f4-bc50-426b-ae0b-08769ecf215b complete Seven sections filled (Reference adaptation).
40 fd82252d-e643-47ea-8ca3-612952761c5a complete No em dashes.
41 c1056fbc-744c-4076-8882-3912ccc68aae complete No hedge words.
42 44f3e05e-9194-46aa-84bc-c5f541d8a94e complete Role references are permission-based throughout.
43 8ee1ad9a-9b37-4db7-b999-1602c5e9363b complete Voice: operator is not the subject of OneClick actions.
44 afd590f3-e33f-4892-ac1e-2ab44dbddcbd complete At a glance strictly v0.3-compliant (no trailing "Read this if/when" guidance).
45 5b1b44d6-0e90-4f53-8ebe-70bf2cc7a946 complete Three-step change process documented.
46 7a628eda-46c0-434c-a6cb-c4d682235850 complete Four-tab structure documented (Instructions, Permissions, Moola, Support).
47 d829c4c5-eee0-4efe-b7ef-3f480092006b complete Distinction from the OneClick product itself called out.
48 d7ca4b52-638c-49b5-9274-fd8b638dee18 complete No real store numbers in body or metadata.
49 d6bf734d-8a84-48b7-a5e4-715765340e25 incomplete UI verified against Production (rubric is external; verify the latest rubric template version against current support process).
50 618a7229-b5dd-4878-b512-9d3dc0aaa30d incomplete Reviewed by Jared and Kevin.