Corporate

By industry

Food and hospitality One screen for every branch’s orders, delivery and invoice. Build and real estate Every purchase tied to its project. Industrial and utilities One set of rules across every region you serve. Trade and movement What the fleet needs, bought the same way everywhere.

Security & control

Your rules, enforced at every branch, logged every time.

Two-factor sign-in, roles and branch scope decide who sees and does what in ENTEK Corporate. Approvers you name sign off every request, and every change is kept with its own timestamp.

  • Sign-in Password + 2FA code
  • Ready-made roles 5, or a custom one
  • Branch scope Full, or one branch only
  • Integration access REST API and MCP

The flow, end to end

  1. 1 Sign in with a password and a second factor
  2. 2 Your role sets what you can do, module by module
  3. 3 Branch scope limits what you see to your own site, or every site
  4. 4 Visibility settings decide which menus even appear
  5. 5 Approvers you name sign off every RFQ and EaaS request
  6. 6 Every sign-off and permission change is kept with its own timestamp
  7. 7 AI drafts and suggests under your own permissions, never on its own
  8. 8 Your own API or MCP connection inherits the same permissions
01

Sign in with a second factor

Every user, set up on their own account

Settings → Security is where two-factor login is turned on. It sits next to, not inside, the roles and permissions pages below.

  1. 1
    Add an authenticator app

    Open Settings → Security and click Add authenticator app, then scan the QR code it shows.

  2. 2
    Confirm the first code

    Enter the first code the app shows to turn two-factor login on for that account.

  3. 3
    Or use an email code instead

    Anyone who has not set up an authenticator app can sign in with a one-time code sent by email.

Rule Two-factor login applies per account, not per role. Every user sets it up the same way.

02

Roles, permissions and branch scope, in one model

Owner or Administrator

User Management is where who-can-do-what is decided: a role sets the default, branch scope narrows it to one site, and a single permission can be adjusted without touching the rest.

  1. 1
    Start from five ready roles, or build one

    Owner, Administrator, Manager, Facility Manager and Engineer each carry a different permission set, shown on Role Assignment with a coverage percentage.

  2. 2
    Limit a person to their own branch

    Set a role to Limited branch access and the person sees and orders for one site only; Full access shows every site on one map.

  3. 3
    Toggle one permission without touching the rest

    Permission Controls lets you switch a single ability, such as View billing, on or off for a role, then Save Changes.

Note The full role-and-permission matrix, with all its detail, lives on Users & roles.

03

Decide which menus even appear

Owner or Administrator

Settings → Visibility is a separate layer from permissions. It decides which sidebar sections show up at all, company-wide or per role.

  1. 1
    Turn on Role Alignment

    Sidebar visibility then follows the same role tree used in Role Assignment, section by section.

  2. 2
    Or set sections by hand

    Turn Role Alignment off, then hide a whole section a branch does not use, or expand it to hide one page inside it.

  3. 3
    Save, and it applies at next sign-in

    Every affected person sees the new sidebar the next time they open ENTEK Corporate.

Note A hidden section stays out of reach even for someone who would otherwise have the matching permission.

04

Approvals before anything leaves the company

Approver: any company user named on the request

An RFQ or an EaaS request names its own approvers on the form itself. Nothing moves to the next stage until every named approver has acted.

  1. 1
    Name one or more approvers on the request

    Choose them from your own company users, under Project & approvals on the RFQ form, or on the EaaS request.

  2. 2
    Each approver reviews and signs off

    RFQ-2417 shows Fahad M. approving at 09:40 and Omar K. at 10:42, each kept in the request’s own record.

  3. 3
    Branch product rules apply at the same time

    A branch can only order what head office assigned to it; an outside product is blocked before checkout, not after.

Rule Suppliers receive an RFQ the moment it is submitted; your internal approval tracks your own sign-off at the same time.

05

Every change kept with its own timestamp

Owner or Administrator reviewing the account

A permission edit, a role change, an approval: each is written to the record the moment it happens, next to the request or account it belongs to.

  1. 1
    A permission change takes effect immediately

    It applies to everyone on that role at once, and may sign an affected person out until they log back in.

  2. 2
    A role edit reaches people already on it, not just new invites

    Change what Engineer can see once, and every Engineer in the company is affected the same way.

  3. 3
    Records stay with the order or request they belong to

    Invoices, the Proof-of-Delivery PDF and contracts are kept next to the order or RFQ they cover, not in one separate archive.

Note Today, each record lives on its own request, order or account page, rather than one combined security log across the whole account.

06

AI and your own integrations, under the same permissions

Every user, for the AI; a developer, for the API or MCP connection

AI inside ENTEK Corporate drafts, suggests and compares. A person still places the order, pays the invoice, approves the RFQ and awards the bid.

  1. 1
    AI helpers work inside the module you are in

    Drafting an RFQ, comparing products or suppliers, and comparing bids all run under your own account’s permissions, nothing wider.

  2. 2
    A person approves and pays, always

    Suggestions and comparisons speed up a decision; awarding a bid, approving a request or paying an invoice stays a human action.

  3. 3
    Connect your own systems by REST API or MCP

    A developer token carries only the permissions of the user who issued it, the same model the in-app AI uses.

Note Scheduled, unattended AI tasks are read-only today.

Who does what

Owner Every permission and branch; the one role that cannot be deleted or handed out by invite
Administrator Manages roles, permissions and visibility; can be named approver on any request
Manager Company-wide procurement and finance approvals, without managing users or roles
Facility Manager Limited to their own branch’s requests and records
Engineer Creates RFQs and tracks orders; approves only when named on a request

Example data shown.

Common questions

What does two-factor login use?

A password plus an authenticator app scanned once with a QR code, or a one-time code sent by email.

Can a branch-scoped person see another branch’s orders or RFQs?

No. Limited branch access shows and allows ordering for their one branch only; a role with Full access sees every site.

Are permission and role changes logged?

Yes. A change takes effect immediately for everyone on that role, and is kept for the account’s own record.

Can we hide menus a company does not use?

Yes. Settings → Visibility aligns the sidebar with roles automatically, or you set each section by hand.

Does AI place orders or approve requests on its own?

No. AI drafts, suggests and compares under your own permissions. A person always places the order, pays, approves and awards.

Can we connect our own ERP or systems to ENTEK Corporate?

Yes, over a governed REST API or MCP interface. A token carries only the permissions of the user who issued it.

Does a supplier see our RFQ before our own approvers sign off?

Yes. Suppliers receive the RFQ the moment it is submitted, while your internal approval tracks your own sign-off at the same time.

Register with ENTEK

Run every branch from one portal. Start with the sites you have today.

Free to start: up to 30 users and 5 branches