Low friction
Employees can use a credential they already know instead of creating and remembering another storefront account.
Storefront access system · case study
A private-store gate that checks eligibility without making shopping feel difficult.
A private employee storefront needed to verify a roster without requiring new accounts. Brent connected an InkSoft access gate to a controlled Google Sheet through Apps Script, supporting case-insensitive PERNR and name matching while keeping the roster out of the storefront interface.
Role disclosure Storefront experience and access-system work completed as part of Data Graphics' client-services workflow. This page does not imply a direct Disney engagement with Eidos Works.
Interactive demonstration
Try the decision point.
This demonstration is isolated from the live store and contains no employee information.
Try an approved example
E
Private team storeEligibility check
Ready
The gate is waiting for a credential.
How it works
A small interface connected to a controlled source of truth.
The visitor sees a simple prompt. The operational logic stays outside the storefront presentation layer.
- 01
Collect
The gate accepts a PERNR or approved name and normalizes spacing and capitalization to reduce avoidable entry errors.
- 02
Verify
A Google Apps Script endpoint compares the submitted value with an authorized Google Sheet roster. The roster is not shipped to the browser.
- 03
Decide
The endpoint returns only the decision needed by the interface. It does not expose the full list or reveal which other records exist.
- 04
Continue
An approved visitor enters the InkSoft store. An unrecognized visitor receives a clear retry path without seeing private merchandise first.
Architecture and evidence
The browser receives a decision—not the employee list.
- Input
- An employee enters a PERNR or approved name. Whitespace and case are normalized before the check.
- Controlled source
- Google Apps Script checks a restricted Google Sheet roster outside the storefront page.
- Response
- The interface receives only an allow or deny result needed to choose the next screen.
- Privacy boundary
- The full roster, Sheet identifier, deployment URL, tokens, private endpoints, and bypass logic are not shipped publicly.
- Observed change
- Approved employees can enter through a credential they already know; unmatched visitors get a retry and support path.
- Unproven
- No conversion, time-saved, employee-count, or security-certification claim is made.
Why it works
The control matches the actual risk and the shopper’s context.
Maintainable roster
Authorized staff can update one Sheet without rebuilding the store or editing the embed whenever eligibility changes.
Minimal disclosure
The browser receives an approval decision rather than a downloadable employee roster.
Platform compatible
The gate adds a tailored access experience around a hosted commerce platform without replacing its ordering and fulfillment tools.
Reusable pattern
The same logic can open the right experience for many kinds of groups.
The interface, source roster, decision rules, and destination can all be adapted to the organization.
Employee merchandise stores
Limit ordering to a current roster while keeping the shopping experience simple for employees.
Schools, teams, and clubs
Confirm a student, family, athlete, or member against an approved list before revealing a private store.
Events and productions
Give cast, crew, volunteers, or attendees access through an event-specific credential or roster.
Dealer and partner portals
Create a lightweight first gate for approved partners before routing them to restricted resources or pricing.
Benefits and allowance programs
Pair roster verification with role, location, or eligibility data to guide people to the correct program.
Preorder and uniform programs
Keep limited ordering windows available to the intended group without forcing every shopper to create an account.
Have a restricted storefront or portal?
Build the smallest access system that responsibly fits the job.
Eidos Works can map the roster, access rules, platform constraints, exception path, and customer experience before choosing the technology.
Discuss an access workflow