Help centre

Full role reference

Setup steps, real workspace links, data checklists, access responsibility and common blockers for every role identifier used by the application.

This guide describes current route names and role boundaries. It is public help, not an access grant, invitation, approval, offer, contract, or confirmation that a workflow or geography is available to your account.

Ask about this page — guided enquiry

Automated fixed-choice form, not a person or live support. A team member reviews submitted enquiries. Opening it sends nothing.

PutYourBrand · Business enquiry

Ask about this page

Automated guided form, not live support. A team member reviews submitted enquiries.

Continue in the full-page formOpening sends nothing. A submitted enquiry may need reconciliation if confirmation fails.

Before you start

An invitation is not an account until the recipient accepts it. Organisation membership, a role grant, geography scope, eligibility and MFA are separate checks. Ask the named authorized issuer for access to the exact organisation and location you need. Sign-in alone does not grant access.

Need an account? Sign in or start from the public enquiry form; neither action self-assigns a role.

Commercial and operational limits

INR 800 per table is an onboarding reference, not a complete commercial contract. Payer, taxes, inclusions, duration, cancellation and other terms require explicit approval. The current benefit resolver blocks incomplete configured lines, but an absent rule may produce no line and no blocker; do not treat an empty benefit matrix as approved or as complete commercial terms. There is no online checkout or automated payment. A reservation does not guarantee installation, footfall, earnings or a completed campaign. These draft terms have not been reviewed by a lawyer; check the version and date shown.

Privacy and safe use

Use only the account, organisation and geography assigned to you. Do not copy secure invitation or resume links into public channels. Contact permission and suppression rules apply; a reminder or draft is not authorization to send. Never submit passwords, MFA recovery codes, payment credentials or unrelated personal data through an enquiry.

Read before you start

Rules and limits you should know before you start

These rules apply to every signed-in account. Each role below repeats them and adds the rules for its own work, so you can read what will be refused before you meet it. Each rule says what is allowed, what is refused, why, and who to ask if you need the refused thing done. Each rule describes how the platform behaves today. A hidden button, a copied link or another role you hold does not change what you are allowed to do.

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.

Step by step

Your pages, in the order you use them

Each page below opens with a guide panel: who it is for, what to have ready, the steps, what happens after you submit and who acts next, common mistakes and where to get help. You can hide the panel on any page; your browser remembers the choice. The order is typical, not mandatory, and a listed page still checks your access when you open it.

Restaurant owner or manager

Onboard the business, set up the venue, negotiate with brands, then host and acknowledge the installation. Binding acceptance is for the bound restaurant owner only.

  1. Business onboarding, step 1 of 9: business details
  2. Business onboarding, steps 2 and 3 of 9: location, business type and guests
  3. Business onboarding, steps 4 and 5 of 9: tables and photos
  4. Business onboarding, steps 6 and 7 of 9: diner offer and advertising rate
  5. Business onboarding, steps 8 and 9 of 9: review, fees and accept
  6. Manage your restaurant team
  7. Manage your venue profiles and display spots
  8. Set up the display spots at each location
  9. Set this location's starting offer (onboarding and diner QR page)
  10. Set up advertising: baseline package and sellable periods
  11. Add photos of this venue
  12. Accept, counter or withdraw in a negotiation
  13. Review your accepted agreements
  14. Check artwork versions and the two-sided proof
  15. Create an installation job
  16. Offer, confirm, cancel or reopen an installation job
  17. Acknowledge the installer's evidence
  18. Reconcile monthly statements

Access rules for this role

Brand owner or operator

Make private offers on venue baselines, accept or counter, then supply artwork and request print work.

  1. Run your brand workspace: destinations, campaigns, offers and agreements
  2. Make an offer on a venue's baseline
  3. Track your offers and negotiations
  4. Accept, counter or withdraw in a negotiation
  5. Review your accepted agreements
  6. Check artwork versions and the two-sided proof
  7. Create a print request for quotes (RFQ)
  8. Compare quotes and choose one
  9. Follow your print work order
  10. Reconcile monthly statements

Access rules for this role

Printer

Enquire, get registered, then quote on matched requests and fulfil only the orders you confirm.

  1. Start or open your print-partner account
  2. Check your print shop profile and qualification
  3. Work your incoming quote requests (RFQs)
  4. Quote or decline one print request
  5. Track the work orders created from your quotes
  6. Confirm, dispatch and record delivery for a work order
  7. Check your print obligations and settlement records

Access rules for this role

Installer

Apply, get qualified, accept a specific job, install, submit evidence, then follow acknowledgement, QA and manual settlement.

  1. Apply to install venue displays
  2. Check your installer application status
  3. Check your installer profile, training and coverage
  4. Review job offers and your accepted installation work
  5. Accept, schedule, start and complete an installation job
  6. Submit installation evidence and share the sign-off link
  7. Check installer earnings and manual settlements

Access rules for this role

City or area manager

Work the scoped queue, assign owners, invite and grant within your contained scope, and route participants to their own binding steps.

  1. Work your city queue
  2. Import leads from CSV
  3. Invite people and manage staff grants
  4. Start assisted onboarding for a restaurant
  5. Read the operational report for your scope

Access rules for this role

Central operations

Coordinate platform-wide onboarding and operations, issue access, assist stuck drafts with consent, review images and resolve exceptions.

  1. Work your city queue
  2. Invite people and manage staff grants
  3. Track restaurant onboarding and assist a stuck draft
  4. Review submitted pictures
  5. Start assisted onboarding for a restaurant
  6. Read the operational report for your scope

Access rules for this role

Sales / BNI coordinator

Manage assigned prospects and follow-ups with documented contact permission; no automatic contact and no assumed referral fee.

  1. Work your city queue
  2. Import leads from CSV

Access rules for this role

Finance reviewer

Review statements and manual reconciliation records independently; nothing on this site transfers money.

  1. Reconcile monthly statements
  2. Read the operational report for your scope

Access rules for this role

QA reviewer

Independently decide restaurant-acknowledged installation evidence; never review your own organisation's work.

  1. Pick up installation evidence for independent QA
  2. Record an independent QA decision

Access rules for this role

Access is checked per action

Choose the role shown on your invitation

One person may hold several roles. A route below is a destination, not proof of permission: each page checks your active grant and scope on arrival. If a link denies access, do not guess IDs or use another account.

Internal role

Platform owner

platform_owner

Global platform configuration and approval, subject to audited controls and separation of approval where required.

Start and setup

Accept an invitation or complete the owner bootstrap, then enrol and verify MFA before internal access.

What to prepare

  • Internal-organisation grant and issuer record
  • MFA enrollment and recovery readiness
  • Approved scope and named task owner

Who grants access

Only an authorized issuer may invite or grant this role; server-side rank, internal-organisation, scope and MFA checks decide each action.

Limits and gotchas

  • A role label or this guide is not a grant.
  • Commercial approval and release gates remain explicit; global access is audited, not silent impersonation.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • Platform owner: sensitive actions need an authenticator code from the last 10 minutes

    Allowed:
    After you enter a current code, sensitive actions run for 10 minutes without asking again.
    Refused:
    Invitations, staff roles, restaurant membership changes, owner recovery, password resets, assisted onboarding and admin commands wait for a fresh code. With no authenticator set up you can only reach /account/security.
    Why:
    The platform owner has the widest authority, so sensitive actions re-check the second factor.
    If you need it done:
    Next actor: you. Next action: enter the current six-digit code in the prompt; the action then runs.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • A PutYourBrand staff account never joins, owns or accepts terms for a restaurant

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators may start an audited assisted onboarding and prepare steps the owner reviews. Finance and QA reviewers cannot.
    Refused:
    An account with any staff role, or a putyourbrand.in email address, cannot be added to a restaurant or accept its agreement, even if it also holds that restaurant's owner role.
    Why:
    Acceptance must come from the restaurant itself.
    If you need it done:
    Next actor: the restaurant owner, on an account with no staff role. Next action: they accept, or add their own non-staff person. Former staff ask central operations to end their staff roles first.
  • Staff roles: who may give which role, where

    Allowed:
    The platform owner, central operations and country, city and area managers give staff roles. Ranks: platform owner 100; central operations, QA reviewer, finance reviewer 90; country manager 60; city manager 40; area manager and sales/BNI coordinator 20. You may give a role of your rank or lower, for a place equal to or inside your own.
    Refused:
    A higher-ranked role; a wider place; a role with no place limit (unless you are platform owner or central operations with no limit); a role for yourself; a role for someone who is not a member of the platform organisation; an expiry that is not in the future. One of your roles must cover all of this by itself.
    Why:
    It stops a manager from choosing who reviews their own work, and stops authority growing beyond what was given.
    If you need it done:
    Next actor: an issuer of equal or higher rank who covers the place (a platform owner for platform owner roles). Next action: they give the role; the person must have accepted a platform invitation first.
  • Staff roles: ending a role takes effect at once, within your rank and place

    Allowed:
    An issuer may end a staff role of equal or lower rank inside their own place. It stops on the holder's next action and is audited with who ended which role and when.
    Refused:
    Ending your own role; ending a higher-ranked role (central operations cannot end a platform owner role); ending a role with no place limit, or outside your place, unless you are platform owner or central operations with no limit.
    Why:
    Roles must be removable quickly, but only by someone who could have given them.
    If you need it done:
    Next actor: central operations (a platform owner for platform owner roles). Next action: they end the role on the Team page.
  • Admin is for the platform owner, central operations and country, city and area managers

    Allowed:
    Those roles open /admin. A manager limited to a place sees and acts on records in that place only.
    Refused:
    Sales/BNI coordinators, finance and QA reviewers and all restaurant, brand, printer and installer accounts. The mail outbox and stuck drafts need a role with no place limit. Password resets and restaurant owner recovery need the platform owner or central operations with no place limit. Restaurant setups with no known city are hidden from managers limited to a place.
    Why:
    Admin changes other people's records, so it is limited to operational roles and their place.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they make the change, or you ask an issuer for the role you need.
  • Admin interventions are named, previewed, reasoned and audited

    Allowed:
    Eight named intervention kinds. Each shows a preview of the current record; you confirm it with a reason code and a reason of 8 to 2,000 characters. Other staff actions (owner recovery, assisted onboarding approvals, staff roles) are separately audited with their own reason rules.
    Refused:
    A confirmation is refused if the record changed after your preview; preview again. There is no general edit or force-complete, and nothing marks identity verified or accepts terms for a participant. Cancelling an outbox email and sending a password reset cannot be undone.
    Why:
    Interventions must keep accepted terms and evidence intact and be traceable.
    If you need it done:
    Next actor: the participant who owns the step, or central operations, through /contact. Next action: route the request to them.
  • Password resets: platform owner or central operations, never for yourself or a higher rank

    Allowed:
    The platform owner or central operations with no place limit can email a one-time reset link (30 minutes) to the account's own address after noting how identity was checked (20 to 1,000 characters).
    Refused:
    Your own password; an account with a higher-ranked role (central operations cannot reset a platform owner); an email with no account (that person needs an invitation). Staff never see the link.
    Why:
    Resets are a takeover risk, so they need an identity check and a record.
    If you need it done:
    Next actor: another platform owner or central operations member of equal or higher rank. Next action: they send the reset from Admin.
  • Workboard: you see and change only leads in your own place

    Allowed:
    Any staff role opens the workboard. Assigning, follow-ups and recording contact permission need a role that can edit: platform owner, central operations, managers and sales/BNI coordinators. Finance and QA reviewers can only read.
    Refused:
    Leads outside your place are not shown. A lead with no city, including every BNI introduction, needs a role with no place limit. You can only assign a lead to someone whose role covers it.
    Why:
    Leads hold personal contact details.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they set the city or pass the lead to someone who covers it.
  • A contact denial is one-way; only a platform owner covering that lead can reverse it

    Allowed:
    Anyone who can edit a lead records permission as granted or not granted, with a basis (up to 120 characters) and evidence (up to 500). Not granted moves the lead to suppressed. A platform owner whose own owner role covers the lead's city or area can reverse a denial with a reason (up to 300 characters); a lead with no city needs an owner role with no place limit. The reversal is recorded against the owner's account with the reason.
    Refused:
    Everyone else, including central operations and managers, cannot reverse a denial. An owner role for another city does not count, even with a manager role for the lead's city: platform owner (Mumbai) plus city manager (Raipur) cannot reverse a Raipur lead. Recording permission never sends a message.
    Why:
    A refusal to be contacted must stick.
    If you need it done:
    Next actor: a platform owner whose role covers the lead's place. Next action: they review the new evidence and record the reversal with it as the reason.
  • Do-not-contact (suppression) entries are add-only, except unverified /unsubscribe entries

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators add an email address with a reason (up to 500 characters); who added it is recorded. Recipients can add their own address on /unsubscribe; it takes effect at once and is recorded as an unverified entry. The same outreach staff may lift an unverified /unsubscribe entry with a reason (10 to 500 characters), for example when the owner of the address asks in writing to receive promotional email again. The lift records who lifted it, when, why and what the entry was. When outreach staff add an address that already has an unverified /unsubscribe entry, that entry becomes a permanent staff entry, recorded with who added it and why.
    Refused:
    Finance and QA reviewers and all restaurant, brand, printer and installer accounts cannot add or lift entries. Entries added by staff, and entries recorded before unverified entries were tracked, can never be lifted. A suppression and a lead's contact denial are separate: record both where both apply.
    Why:
    An opt-out must never be quietly reversed; only an entry nobody verified can be lifted, and only on the record.
    If you need it done:
    Next actor: one of the outreach staff named above. Next action: they add the address, or lift an unverified /unsubscribe entry with a reason (POST /api/suppressions/lift).
  • Inbound enquiry permission is specific; drafts, reminders and imports are not permission

    Allowed:
    Follow-ups, assignments, reminders and imports are internal records only.
    Refused:
    An enquiry submitted on /enquiry or the guided form records permission to respond to that enquiry, with source and timestamp; there is no separate opt-in. An existing denial, do-not-contact stage or suppressed address is not reopened by submission. The receipt is queued when an email is supplied, subject to identity and rate limits, and suppressed addresses cannot receive it. No feature sends promotional outreach email or WhatsApp. Imported leads start with permission unknown. BNI membership is not consent. Do not import scraped or gated-directory contacts. Decision: 5 October 2026.
    Why:
    A person's own submitted enquiry documents their request for an enquiry-specific reply, not promotional permission. Imports and drafts do not document that request.
    If you need it done:
    Next actor: the lead owner. Next action: check existing denial and suppression before responding to an inbound enquiry; for imported leads, record documented permission before one-to-one contact outside the platform.
  • Lead import: every row must be in a city you can edit

    Allowed:
    Paste CSV, preview, then commit. Only you can commit your preview, within 30 minutes.
    Refused:
    Rows in cities you cannot edit are left out (finance and QA reviewers cannot edit, so all their rows are left out). Duplicates are checked against all leads, including ones you cannot see. If your role changes between preview and commit, the commit is refused.
    Why:
    Import creates personal-data records under the same place rule as manual edits.
    If you need it done:
    Next actor: a colleague who covers the left-out rows, or central operations. Next action: give them only those rows.
  • Lead export: only some roles, only for their own place

    Allowed:
    Platform owner, central operations, managers and finance reviewers export leads for a city they cover. Exporting every city needs a role with no place limit.
    Refused:
    Sales/BNI coordinators and QA reviewers cannot export. "Export my leads" shows only leads you can export, which may be none.
    Why:
    Exporting copies personal data out of the platform.
    If you need it done:
    Next actor: your city manager or central operations. Next action: they run the export.
  • Assisted onboarding: recorded consent, operator invitation, owner acceptance

    Allowed:
    Platform owner and central operations anywhere; managers, sales/BNI coordinators and place-limited owner or operations roles in their own place. Record the consent channel, a statement of 12 to 500 characters and the owner's email.
    Refused:
    Suppressed, converted or dead leads; leads with unknown city for scoped roles; company or staff owner email. Cancellation is allowed only before owner acceptance and revokes the link, not mail already delivered.
    Why:
    Recorded consent, scoped staff access, a bound email-only invitation and owner-only acceptance protect the handover.
    If you need it done:
    Next actor: the restaurant owner. Next action: open the invitation, review the application and accept personally. Central operations resolves mail delivery failures.
  • Restaurant owner recovery: two staff members, only when no owner is active

    Allowed:
    The platform owner or central operations with no place limit start a recovery for a restaurant that had an owner and now has none, with consent and a reason of 12 to 500 characters.
    Refused:
    A restaurant with an active owner (that owner invites people); one that never had an owner (use assisted onboarding); a second recovery while one is pending; approval by the person who started it.
    Why:
    Handing a restaurant to a new owner is the biggest account change a participant can face.
    If you need it done:
    Next actor: a second platform-wide staff member. Next action: approve or decline the pending recovery in Admin.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • Recording a settlement: INR only, once, and not by the person who recorded the work

    Allowed:
    The platform owner or central operations covering the place record a settlement of an installer earning or a printer obligation in INR, with an external reference (3 to 200 characters) and a repeat-protection key.
    Refused:
    A repeated key; more than is owed; an earning that is on hold or disputed, or whose installation job has an open dispute; the person who recorded the work or attached its documents; an operator who belongs to the paid organisation. Settled records are final.
    Why:
    A settlement record is the evidence of payment, so it must be unique, bounded and independent.
    If you need it done:
    Next actor: a different operator with no tie to the organisation, after any hold or dispute is resolved. Next action: they record it.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Brand, print partner and installer teams: staff bring in the first owner; the owner adds the team

    Allowed:
    Central operations or the platform owner may invite the first owner of a brand, print partner or installer organisation that has no active owner, and the same path restores an owner when an organisation has lost every owner. Applying as a print partner or installer makes the applicant the owner. Once there is an owner, the owner invites co-owners and operators (installer workers for installers) from the Team page (/dashboard/team). Operators keep their earlier right to invite operators. Owners without staff roles remove non-owner members or end non-owner roles on the Team page. Central operations or a platform owner covering every registered place may remove non-owner access there; only an unrestricted central operations or platform owner grant may end owner access. Each change is audited. Ending membership ends all roles immediately, including for an already signed-in person on the next request.
    Refused:
    Once the organisation has an active owner, PutYourBrand staff cannot add anyone or give anyone a role there, including an owner whose account also holds a staff role (refused as staff_cannot_add_members). An invitation issued by staff, or with no recorded issuer, is refused and stays unused if an owner joined before acceptance; a later end to the issuer's staff role does not unlock it. Only an active owner with no staff role makes someone a co-owner. On the Team page an active owner without a staff role removes a non-owner member or ends a non-owner role. Ending a membership ends all its roles in the same transaction; every change is audited. Central operations or a platform owner may remove members and end non-owner roles where one role covers the whole organisation (an unrestricted role, or one scoped role covering all registered places). Only an unrestricted one may end an owner role or membership. An owner cannot end their own last owner role; staff must end any owner role. A staff-and-owner account acts as staff, not as a non-staff owner.
    Why:
    Brands, print partners and installers agree terms that bind them, so who acts for them is their owner's decision, as for restaurants.
    If you need it done:
    Next actor: an owner of your organisation (invitations and non-owner removal from /dashboard/team), or central operations, through /contact for owner removal or an organisation with no owner. Next action: they make the audited change; a removed person's existing session no longer has those roles on its next request.
  • Pictures: fixed limits and staff review

    Allowed:
    Up to 12 photos per venue location, 3 per display spot, and one logo plus one replacement waiting for review. Approved venue photos and logos are public; display spot photos stay internal.
    Refused:
    Rejected pictures count toward the limit until removed. Editing an approved picture's description takes it off the public page until reviewed again. Nobody reviews their own upload or a picture from their own organisation.
    Why:
    Public pictures must respect rights, consent and accuracy.
    If you need it done:
    Next actor: platform staff covering your city. Next action: they approve the picture or reject it with a reason.
  • A placement goes live only when all seven steps are done

    Allowed:
    The restaurant owner, brand owner or a platform operator activates once there are approved terms, an approved proof, a confirmed print order, a completed installation, the venue sign-off, independent QA and a recorded settlement of the installer's earning.
    Refused:
    Operators and managers cannot activate. A staff waiver blocks a step rather than completing it. Activation is final; pausing is the only reverse, and resuming re-checks every step.
    Why:
    Going live is where every earlier step must be shown.
    If you need it done:
    Next actor: whoever owns the first missing step, named on the activation panel. Next action: complete it, then retry.
  • Installer earnings: accepted work only, never scans, settled by hand

    Allowed:
    You are paid for the smaller of the venue-accepted and QA-accepted counts on the same evidence. Earnings appear after central operations recomputes them, and are settled by a record after payment outside the platform.
    Refused:
    QR scans never create earnings. Self-reported work alone is never paid. An earning on hold or disputed, or whose job has an open dispute, cannot be settled until that is resolved. A cancelled job's unsettled earnings are withdrawn at the next recompute. The person who sent the evidence, the QA reviewer and anyone in the installer organisation cannot record the settlement. No amount or date is promised.
    Why:
    Pay follows independently accepted work.
    If you need it done:
    Next actor: central operations. Next action: resolve any hold or dispute, recompute earnings and record the settlement once paid.

Next actor and action: Next actor: an authorized internal-role issuer. Next action: issue the least-privilege grant and confirm the recipient completes MFA.

Internal role

Central operations

central_operations

Coordinate approved onboarding and operations across the platform scope; this role cannot change approved commercial history or grant platform-owner authority.

Start and setup

Accept an internal invitation and sign in with your password. An authenticator is optional (set one up at /account/security); only the platform owner must use one.

What to prepare

  • Internal organisation and active grant
  • Task geography, reason and required evidence
  • Independent review for money, QA or ownerless recovery where required

Who grants access

Internal-role issuers grant this role subject to the rank/scope rules. Central operations cannot grant platform_owner.

Limits and gotchas

  • Organisation membership and role grant are separate records.
  • Admin assistance never verifies identity or accepts commercial terms for a participant.
  • Central operations cannot invite or grant the restaurant owner role. A new restaurant's owner is invited only through Start assisted onboarding (the link is emailed to the owner and never shown to staff); later owners are added by an existing owner of that restaurant.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • A PutYourBrand staff account never joins, owns or accepts terms for a restaurant

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators may start an audited assisted onboarding and prepare steps the owner reviews. Finance and QA reviewers cannot.
    Refused:
    An account with any staff role, or a putyourbrand.in email address, cannot be added to a restaurant or accept its agreement, even if it also holds that restaurant's owner role.
    Why:
    Acceptance must come from the restaurant itself.
    If you need it done:
    Next actor: the restaurant owner, on an account with no staff role. Next action: they accept, or add their own non-staff person. Former staff ask central operations to end their staff roles first.
  • Staff roles: who may give which role, where

    Allowed:
    The platform owner, central operations and country, city and area managers give staff roles. Ranks: platform owner 100; central operations, QA reviewer, finance reviewer 90; country manager 60; city manager 40; area manager and sales/BNI coordinator 20. You may give a role of your rank or lower, for a place equal to or inside your own.
    Refused:
    A higher-ranked role; a wider place; a role with no place limit (unless you are platform owner or central operations with no limit); a role for yourself; a role for someone who is not a member of the platform organisation; an expiry that is not in the future. One of your roles must cover all of this by itself.
    Why:
    It stops a manager from choosing who reviews their own work, and stops authority growing beyond what was given.
    If you need it done:
    Next actor: an issuer of equal or higher rank who covers the place (a platform owner for platform owner roles). Next action: they give the role; the person must have accepted a platform invitation first.
  • Staff roles: ending a role takes effect at once, within your rank and place

    Allowed:
    An issuer may end a staff role of equal or lower rank inside their own place. It stops on the holder's next action and is audited with who ended which role and when.
    Refused:
    Ending your own role; ending a higher-ranked role (central operations cannot end a platform owner role); ending a role with no place limit, or outside your place, unless you are platform owner or central operations with no limit.
    Why:
    Roles must be removable quickly, but only by someone who could have given them.
    If you need it done:
    Next actor: central operations (a platform owner for platform owner roles). Next action: they end the role on the Team page.
  • Admin is for the platform owner, central operations and country, city and area managers

    Allowed:
    Those roles open /admin. A manager limited to a place sees and acts on records in that place only.
    Refused:
    Sales/BNI coordinators, finance and QA reviewers and all restaurant, brand, printer and installer accounts. The mail outbox and stuck drafts need a role with no place limit. Password resets and restaurant owner recovery need the platform owner or central operations with no place limit. Restaurant setups with no known city are hidden from managers limited to a place.
    Why:
    Admin changes other people's records, so it is limited to operational roles and their place.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they make the change, or you ask an issuer for the role you need.
  • Admin interventions are named, previewed, reasoned and audited

    Allowed:
    Eight named intervention kinds. Each shows a preview of the current record; you confirm it with a reason code and a reason of 8 to 2,000 characters. Other staff actions (owner recovery, assisted onboarding approvals, staff roles) are separately audited with their own reason rules.
    Refused:
    A confirmation is refused if the record changed after your preview; preview again. There is no general edit or force-complete, and nothing marks identity verified or accepts terms for a participant. Cancelling an outbox email and sending a password reset cannot be undone.
    Why:
    Interventions must keep accepted terms and evidence intact and be traceable.
    If you need it done:
    Next actor: the participant who owns the step, or central operations, through /contact. Next action: route the request to them.
  • Password resets: platform owner or central operations, never for yourself or a higher rank

    Allowed:
    The platform owner or central operations with no place limit can email a one-time reset link (30 minutes) to the account's own address after noting how identity was checked (20 to 1,000 characters).
    Refused:
    Your own password; an account with a higher-ranked role (central operations cannot reset a platform owner); an email with no account (that person needs an invitation). Staff never see the link.
    Why:
    Resets are a takeover risk, so they need an identity check and a record.
    If you need it done:
    Next actor: another platform owner or central operations member of equal or higher rank. Next action: they send the reset from Admin.
  • Workboard: you see and change only leads in your own place

    Allowed:
    Any staff role opens the workboard. Assigning, follow-ups and recording contact permission need a role that can edit: platform owner, central operations, managers and sales/BNI coordinators. Finance and QA reviewers can only read.
    Refused:
    Leads outside your place are not shown. A lead with no city, including every BNI introduction, needs a role with no place limit. You can only assign a lead to someone whose role covers it.
    Why:
    Leads hold personal contact details.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they set the city or pass the lead to someone who covers it.
  • A contact denial is one-way; only a platform owner covering that lead can reverse it

    Allowed:
    Anyone who can edit a lead records permission as granted or not granted, with a basis (up to 120 characters) and evidence (up to 500). Not granted moves the lead to suppressed. A platform owner whose own owner role covers the lead's city or area can reverse a denial with a reason (up to 300 characters); a lead with no city needs an owner role with no place limit. The reversal is recorded against the owner's account with the reason.
    Refused:
    Everyone else, including central operations and managers, cannot reverse a denial. An owner role for another city does not count, even with a manager role for the lead's city: platform owner (Mumbai) plus city manager (Raipur) cannot reverse a Raipur lead. Recording permission never sends a message.
    Why:
    A refusal to be contacted must stick.
    If you need it done:
    Next actor: a platform owner whose role covers the lead's place. Next action: they review the new evidence and record the reversal with it as the reason.
  • Do-not-contact (suppression) entries are add-only, except unverified /unsubscribe entries

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators add an email address with a reason (up to 500 characters); who added it is recorded. Recipients can add their own address on /unsubscribe; it takes effect at once and is recorded as an unverified entry. The same outreach staff may lift an unverified /unsubscribe entry with a reason (10 to 500 characters), for example when the owner of the address asks in writing to receive promotional email again. The lift records who lifted it, when, why and what the entry was. When outreach staff add an address that already has an unverified /unsubscribe entry, that entry becomes a permanent staff entry, recorded with who added it and why.
    Refused:
    Finance and QA reviewers and all restaurant, brand, printer and installer accounts cannot add or lift entries. Entries added by staff, and entries recorded before unverified entries were tracked, can never be lifted. A suppression and a lead's contact denial are separate: record both where both apply.
    Why:
    An opt-out must never be quietly reversed; only an entry nobody verified can be lifted, and only on the record.
    If you need it done:
    Next actor: one of the outreach staff named above. Next action: they add the address, or lift an unverified /unsubscribe entry with a reason (POST /api/suppressions/lift).
  • Inbound enquiry permission is specific; drafts, reminders and imports are not permission

    Allowed:
    Follow-ups, assignments, reminders and imports are internal records only.
    Refused:
    An enquiry submitted on /enquiry or the guided form records permission to respond to that enquiry, with source and timestamp; there is no separate opt-in. An existing denial, do-not-contact stage or suppressed address is not reopened by submission. The receipt is queued when an email is supplied, subject to identity and rate limits, and suppressed addresses cannot receive it. No feature sends promotional outreach email or WhatsApp. Imported leads start with permission unknown. BNI membership is not consent. Do not import scraped or gated-directory contacts. Decision: 5 October 2026.
    Why:
    A person's own submitted enquiry documents their request for an enquiry-specific reply, not promotional permission. Imports and drafts do not document that request.
    If you need it done:
    Next actor: the lead owner. Next action: check existing denial and suppression before responding to an inbound enquiry; for imported leads, record documented permission before one-to-one contact outside the platform.
  • Lead import: every row must be in a city you can edit

    Allowed:
    Paste CSV, preview, then commit. Only you can commit your preview, within 30 minutes.
    Refused:
    Rows in cities you cannot edit are left out (finance and QA reviewers cannot edit, so all their rows are left out). Duplicates are checked against all leads, including ones you cannot see. If your role changes between preview and commit, the commit is refused.
    Why:
    Import creates personal-data records under the same place rule as manual edits.
    If you need it done:
    Next actor: a colleague who covers the left-out rows, or central operations. Next action: give them only those rows.
  • Lead export: only some roles, only for their own place

    Allowed:
    Platform owner, central operations, managers and finance reviewers export leads for a city they cover. Exporting every city needs a role with no place limit.
    Refused:
    Sales/BNI coordinators and QA reviewers cannot export. "Export my leads" shows only leads you can export, which may be none.
    Why:
    Exporting copies personal data out of the platform.
    If you need it done:
    Next actor: your city manager or central operations. Next action: they run the export.
  • Assisted onboarding: recorded consent, operator invitation, owner acceptance

    Allowed:
    Platform owner and central operations anywhere; managers, sales/BNI coordinators and place-limited owner or operations roles in their own place. Record the consent channel, a statement of 12 to 500 characters and the owner's email.
    Refused:
    Suppressed, converted or dead leads; leads with unknown city for scoped roles; company or staff owner email. Cancellation is allowed only before owner acceptance and revokes the link, not mail already delivered.
    Why:
    Recorded consent, scoped staff access, a bound email-only invitation and owner-only acceptance protect the handover.
    If you need it done:
    Next actor: the restaurant owner. Next action: open the invitation, review the application and accept personally. Central operations resolves mail delivery failures.
  • Restaurant owner recovery: two staff members, only when no owner is active

    Allowed:
    The platform owner or central operations with no place limit start a recovery for a restaurant that had an owner and now has none, with consent and a reason of 12 to 500 characters.
    Refused:
    A restaurant with an active owner (that owner invites people); one that never had an owner (use assisted onboarding); a second recovery while one is pending; approval by the person who started it.
    Why:
    Handing a restaurant to a new owner is the biggest account change a participant can face.
    If you need it done:
    Next actor: a second platform-wide staff member. Next action: approve or decline the pending recovery in Admin.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • Recording a settlement: INR only, once, and not by the person who recorded the work

    Allowed:
    The platform owner or central operations covering the place record a settlement of an installer earning or a printer obligation in INR, with an external reference (3 to 200 characters) and a repeat-protection key.
    Refused:
    A repeated key; more than is owed; an earning that is on hold or disputed, or whose installation job has an open dispute; the person who recorded the work or attached its documents; an operator who belongs to the paid organisation. Settled records are final.
    Why:
    A settlement record is the evidence of payment, so it must be unique, bounded and independent.
    If you need it done:
    Next actor: a different operator with no tie to the organisation, after any hold or dispute is resolved. Next action: they record it.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Brand, print partner and installer teams: staff bring in the first owner; the owner adds the team

    Allowed:
    Central operations or the platform owner may invite the first owner of a brand, print partner or installer organisation that has no active owner, and the same path restores an owner when an organisation has lost every owner. Applying as a print partner or installer makes the applicant the owner. Once there is an owner, the owner invites co-owners and operators (installer workers for installers) from the Team page (/dashboard/team). Operators keep their earlier right to invite operators. Owners without staff roles remove non-owner members or end non-owner roles on the Team page. Central operations or a platform owner covering every registered place may remove non-owner access there; only an unrestricted central operations or platform owner grant may end owner access. Each change is audited. Ending membership ends all roles immediately, including for an already signed-in person on the next request.
    Refused:
    Once the organisation has an active owner, PutYourBrand staff cannot add anyone or give anyone a role there, including an owner whose account also holds a staff role (refused as staff_cannot_add_members). An invitation issued by staff, or with no recorded issuer, is refused and stays unused if an owner joined before acceptance; a later end to the issuer's staff role does not unlock it. Only an active owner with no staff role makes someone a co-owner. On the Team page an active owner without a staff role removes a non-owner member or ends a non-owner role. Ending a membership ends all its roles in the same transaction; every change is audited. Central operations or a platform owner may remove members and end non-owner roles where one role covers the whole organisation (an unrestricted role, or one scoped role covering all registered places). Only an unrestricted one may end an owner role or membership. An owner cannot end their own last owner role; staff must end any owner role. A staff-and-owner account acts as staff, not as a non-staff owner.
    Why:
    Brands, print partners and installers agree terms that bind them, so who acts for them is their owner's decision, as for restaurants.
    If you need it done:
    Next actor: an owner of your organisation (invitations and non-owner removal from /dashboard/team), or central operations, through /contact for owner removal or an organisation with no owner. Next action: they make the audited change; a removed person's existing session no longer has those roles on its next request.
  • Pictures: fixed limits and staff review

    Allowed:
    Up to 12 photos per venue location, 3 per display spot, and one logo plus one replacement waiting for review. Approved venue photos and logos are public; display spot photos stay internal.
    Refused:
    Rejected pictures count toward the limit until removed. Editing an approved picture's description takes it off the public page until reviewed again. Nobody reviews their own upload or a picture from their own organisation.
    Why:
    Public pictures must respect rights, consent and accuracy.
    If you need it done:
    Next actor: platform staff covering your city. Next action: they approve the picture or reject it with a reason.
  • A placement goes live only when all seven steps are done

    Allowed:
    The restaurant owner, brand owner or a platform operator activates once there are approved terms, an approved proof, a confirmed print order, a completed installation, the venue sign-off, independent QA and a recorded settlement of the installer's earning.
    Refused:
    Operators and managers cannot activate. A staff waiver blocks a step rather than completing it. Activation is final; pausing is the only reverse, and resuming re-checks every step.
    Why:
    Going live is where every earlier step must be shown.
    If you need it done:
    Next actor: whoever owns the first missing step, named on the activation panel. Next action: complete it, then retry.
  • Installer earnings: accepted work only, never scans, settled by hand

    Allowed:
    You are paid for the smaller of the venue-accepted and QA-accepted counts on the same evidence. Earnings appear after central operations recomputes them, and are settled by a record after payment outside the platform.
    Refused:
    QR scans never create earnings. Self-reported work alone is never paid. An earning on hold or disputed, or whose job has an open dispute, cannot be settled until that is resolved. A cancelled job's unsettled earnings are withdrawn at the next recompute. The person who sent the evidence, the QA reviewer and anyone in the installer organisation cannot record the settlement. No amount or date is promised.
    Why:
    Pay follows independently accepted work.
    If you need it done:
    Next actor: central operations. Next action: resolve any hold or dispute, recompute earnings and record the settlement once paid.

Next actor and action: Next actor: the authorized issuer or assigned participant. Next action: issue/accept the scoped access, then complete the assigned reviewed task.

Internal role

Country manager

country_manager

Operate only within the assigned country subtree; no access to another country or independent platform-pricing authority.

Start and setup

Accept the internal invitation and check the country scope shown on your grant. An authenticator is optional (set one up at /account/security); only the platform owner must use one.

What to prepare

  • Internal organisation membership
  • Country geography grant and expiry
  • Current task and escalation contact

Who grants access

An authorized higher/equal-rank internal issuer may grant access within contained scope; each request is rechecked server-side.

Limits and gotchas

  • A country name or URL does not establish access.
  • Country managers cannot approve their own payable work.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • A PutYourBrand staff account never joins, owns or accepts terms for a restaurant

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators may start an audited assisted onboarding and prepare steps the owner reviews. Finance and QA reviewers cannot.
    Refused:
    An account with any staff role, or a putyourbrand.in email address, cannot be added to a restaurant or accept its agreement, even if it also holds that restaurant's owner role.
    Why:
    Acceptance must come from the restaurant itself.
    If you need it done:
    Next actor: the restaurant owner, on an account with no staff role. Next action: they accept, or add their own non-staff person. Former staff ask central operations to end their staff roles first.
  • Staff roles: who may give which role, where

    Allowed:
    The platform owner, central operations and country, city and area managers give staff roles. Ranks: platform owner 100; central operations, QA reviewer, finance reviewer 90; country manager 60; city manager 40; area manager and sales/BNI coordinator 20. You may give a role of your rank or lower, for a place equal to or inside your own.
    Refused:
    A higher-ranked role; a wider place; a role with no place limit (unless you are platform owner or central operations with no limit); a role for yourself; a role for someone who is not a member of the platform organisation; an expiry that is not in the future. One of your roles must cover all of this by itself.
    Why:
    It stops a manager from choosing who reviews their own work, and stops authority growing beyond what was given.
    If you need it done:
    Next actor: an issuer of equal or higher rank who covers the place (a platform owner for platform owner roles). Next action: they give the role; the person must have accepted a platform invitation first.
  • Staff roles: ending a role takes effect at once, within your rank and place

    Allowed:
    An issuer may end a staff role of equal or lower rank inside their own place. It stops on the holder's next action and is audited with who ended which role and when.
    Refused:
    Ending your own role; ending a higher-ranked role (central operations cannot end a platform owner role); ending a role with no place limit, or outside your place, unless you are platform owner or central operations with no limit.
    Why:
    Roles must be removable quickly, but only by someone who could have given them.
    If you need it done:
    Next actor: central operations (a platform owner for platform owner roles). Next action: they end the role on the Team page.
  • Admin is for the platform owner, central operations and country, city and area managers

    Allowed:
    Those roles open /admin. A manager limited to a place sees and acts on records in that place only.
    Refused:
    Sales/BNI coordinators, finance and QA reviewers and all restaurant, brand, printer and installer accounts. The mail outbox and stuck drafts need a role with no place limit. Password resets and restaurant owner recovery need the platform owner or central operations with no place limit. Restaurant setups with no known city are hidden from managers limited to a place.
    Why:
    Admin changes other people's records, so it is limited to operational roles and their place.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they make the change, or you ask an issuer for the role you need.
  • Admin interventions are named, previewed, reasoned and audited

    Allowed:
    Eight named intervention kinds. Each shows a preview of the current record; you confirm it with a reason code and a reason of 8 to 2,000 characters. Other staff actions (owner recovery, assisted onboarding approvals, staff roles) are separately audited with their own reason rules.
    Refused:
    A confirmation is refused if the record changed after your preview; preview again. There is no general edit or force-complete, and nothing marks identity verified or accepts terms for a participant. Cancelling an outbox email and sending a password reset cannot be undone.
    Why:
    Interventions must keep accepted terms and evidence intact and be traceable.
    If you need it done:
    Next actor: the participant who owns the step, or central operations, through /contact. Next action: route the request to them.
  • Workboard: you see and change only leads in your own place

    Allowed:
    Any staff role opens the workboard. Assigning, follow-ups and recording contact permission need a role that can edit: platform owner, central operations, managers and sales/BNI coordinators. Finance and QA reviewers can only read.
    Refused:
    Leads outside your place are not shown. A lead with no city, including every BNI introduction, needs a role with no place limit. You can only assign a lead to someone whose role covers it.
    Why:
    Leads hold personal contact details.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they set the city or pass the lead to someone who covers it.
  • A contact denial is one-way; only a platform owner covering that lead can reverse it

    Allowed:
    Anyone who can edit a lead records permission as granted or not granted, with a basis (up to 120 characters) and evidence (up to 500). Not granted moves the lead to suppressed. A platform owner whose own owner role covers the lead's city or area can reverse a denial with a reason (up to 300 characters); a lead with no city needs an owner role with no place limit. The reversal is recorded against the owner's account with the reason.
    Refused:
    Everyone else, including central operations and managers, cannot reverse a denial. An owner role for another city does not count, even with a manager role for the lead's city: platform owner (Mumbai) plus city manager (Raipur) cannot reverse a Raipur lead. Recording permission never sends a message.
    Why:
    A refusal to be contacted must stick.
    If you need it done:
    Next actor: a platform owner whose role covers the lead's place. Next action: they review the new evidence and record the reversal with it as the reason.
  • Do-not-contact (suppression) entries are add-only, except unverified /unsubscribe entries

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators add an email address with a reason (up to 500 characters); who added it is recorded. Recipients can add their own address on /unsubscribe; it takes effect at once and is recorded as an unverified entry. The same outreach staff may lift an unverified /unsubscribe entry with a reason (10 to 500 characters), for example when the owner of the address asks in writing to receive promotional email again. The lift records who lifted it, when, why and what the entry was. When outreach staff add an address that already has an unverified /unsubscribe entry, that entry becomes a permanent staff entry, recorded with who added it and why.
    Refused:
    Finance and QA reviewers and all restaurant, brand, printer and installer accounts cannot add or lift entries. Entries added by staff, and entries recorded before unverified entries were tracked, can never be lifted. A suppression and a lead's contact denial are separate: record both where both apply.
    Why:
    An opt-out must never be quietly reversed; only an entry nobody verified can be lifted, and only on the record.
    If you need it done:
    Next actor: one of the outreach staff named above. Next action: they add the address, or lift an unverified /unsubscribe entry with a reason (POST /api/suppressions/lift).
  • Inbound enquiry permission is specific; drafts, reminders and imports are not permission

    Allowed:
    Follow-ups, assignments, reminders and imports are internal records only.
    Refused:
    An enquiry submitted on /enquiry or the guided form records permission to respond to that enquiry, with source and timestamp; there is no separate opt-in. An existing denial, do-not-contact stage or suppressed address is not reopened by submission. The receipt is queued when an email is supplied, subject to identity and rate limits, and suppressed addresses cannot receive it. No feature sends promotional outreach email or WhatsApp. Imported leads start with permission unknown. BNI membership is not consent. Do not import scraped or gated-directory contacts. Decision: 5 October 2026.
    Why:
    A person's own submitted enquiry documents their request for an enquiry-specific reply, not promotional permission. Imports and drafts do not document that request.
    If you need it done:
    Next actor: the lead owner. Next action: check existing denial and suppression before responding to an inbound enquiry; for imported leads, record documented permission before one-to-one contact outside the platform.
  • Lead import: every row must be in a city you can edit

    Allowed:
    Paste CSV, preview, then commit. Only you can commit your preview, within 30 minutes.
    Refused:
    Rows in cities you cannot edit are left out (finance and QA reviewers cannot edit, so all their rows are left out). Duplicates are checked against all leads, including ones you cannot see. If your role changes between preview and commit, the commit is refused.
    Why:
    Import creates personal-data records under the same place rule as manual edits.
    If you need it done:
    Next actor: a colleague who covers the left-out rows, or central operations. Next action: give them only those rows.
  • Lead export: only some roles, only for their own place

    Allowed:
    Platform owner, central operations, managers and finance reviewers export leads for a city they cover. Exporting every city needs a role with no place limit.
    Refused:
    Sales/BNI coordinators and QA reviewers cannot export. "Export my leads" shows only leads you can export, which may be none.
    Why:
    Exporting copies personal data out of the platform.
    If you need it done:
    Next actor: your city manager or central operations. Next action: they run the export.
  • Assisted onboarding: recorded consent, operator invitation, owner acceptance

    Allowed:
    Platform owner and central operations anywhere; managers, sales/BNI coordinators and place-limited owner or operations roles in their own place. Record the consent channel, a statement of 12 to 500 characters and the owner's email.
    Refused:
    Suppressed, converted or dead leads; leads with unknown city for scoped roles; company or staff owner email. Cancellation is allowed only before owner acceptance and revokes the link, not mail already delivered.
    Why:
    Recorded consent, scoped staff access, a bound email-only invitation and owner-only acceptance protect the handover.
    If you need it done:
    Next actor: the restaurant owner. Next action: open the invitation, review the application and accept personally. Central operations resolves mail delivery failures.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Pictures: fixed limits and staff review

    Allowed:
    Up to 12 photos per venue location, 3 per display spot, and one logo plus one replacement waiting for review. Approved venue photos and logos are public; display spot photos stay internal.
    Refused:
    Rejected pictures count toward the limit until removed. Editing an approved picture's description takes it off the public page until reviewed again. Nobody reviews their own upload or a picture from their own organisation.
    Why:
    Public pictures must respect rights, consent and accuracy.
    If you need it done:
    Next actor: platform staff covering your city. Next action: they approve the picture or reject it with a reason.

Next actor and action: Next actor: the internal issuer. Next action: confirm the country grant is active; escalate cross-country work to central operations.

Internal role

City manager

city_manager

Coordinate work and authorized local review in the granted city and its areas.

Start and setup

Accept an internal invitation and verify the city scope before working a queue. An authenticator is optional (set one up at /account/security); only the platform owner must use one.

What to prepare

  • Internal membership and active city grant
  • Current assignment and next action
  • Any independent-review conflict

Who grants access

Internal-role issuers may grant only within their own authority and contained scope; grants are audited and revocable.

Limits and gotchas

  • City scope is structured geography, not text or BNI chapter membership.
  • The /admin assistance queue requires platform-wide read scope; city/area-only grants cannot see it. Local wizard assistance is not available there.
  • Do not self-approve installer earnings or settlements.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • A PutYourBrand staff account never joins, owns or accepts terms for a restaurant

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators may start an audited assisted onboarding and prepare steps the owner reviews. Finance and QA reviewers cannot.
    Refused:
    An account with any staff role, or a putyourbrand.in email address, cannot be added to a restaurant or accept its agreement, even if it also holds that restaurant's owner role.
    Why:
    Acceptance must come from the restaurant itself.
    If you need it done:
    Next actor: the restaurant owner, on an account with no staff role. Next action: they accept, or add their own non-staff person. Former staff ask central operations to end their staff roles first.
  • Staff roles: who may give which role, where

    Allowed:
    The platform owner, central operations and country, city and area managers give staff roles. Ranks: platform owner 100; central operations, QA reviewer, finance reviewer 90; country manager 60; city manager 40; area manager and sales/BNI coordinator 20. You may give a role of your rank or lower, for a place equal to or inside your own.
    Refused:
    A higher-ranked role; a wider place; a role with no place limit (unless you are platform owner or central operations with no limit); a role for yourself; a role for someone who is not a member of the platform organisation; an expiry that is not in the future. One of your roles must cover all of this by itself.
    Why:
    It stops a manager from choosing who reviews their own work, and stops authority growing beyond what was given.
    If you need it done:
    Next actor: an issuer of equal or higher rank who covers the place (a platform owner for platform owner roles). Next action: they give the role; the person must have accepted a platform invitation first.
  • Staff roles: ending a role takes effect at once, within your rank and place

    Allowed:
    An issuer may end a staff role of equal or lower rank inside their own place. It stops on the holder's next action and is audited with who ended which role and when.
    Refused:
    Ending your own role; ending a higher-ranked role (central operations cannot end a platform owner role); ending a role with no place limit, or outside your place, unless you are platform owner or central operations with no limit.
    Why:
    Roles must be removable quickly, but only by someone who could have given them.
    If you need it done:
    Next actor: central operations (a platform owner for platform owner roles). Next action: they end the role on the Team page.
  • Admin is for the platform owner, central operations and country, city and area managers

    Allowed:
    Those roles open /admin. A manager limited to a place sees and acts on records in that place only.
    Refused:
    Sales/BNI coordinators, finance and QA reviewers and all restaurant, brand, printer and installer accounts. The mail outbox and stuck drafts need a role with no place limit. Password resets and restaurant owner recovery need the platform owner or central operations with no place limit. Restaurant setups with no known city are hidden from managers limited to a place.
    Why:
    Admin changes other people's records, so it is limited to operational roles and their place.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they make the change, or you ask an issuer for the role you need.
  • Admin interventions are named, previewed, reasoned and audited

    Allowed:
    Eight named intervention kinds. Each shows a preview of the current record; you confirm it with a reason code and a reason of 8 to 2,000 characters. Other staff actions (owner recovery, assisted onboarding approvals, staff roles) are separately audited with their own reason rules.
    Refused:
    A confirmation is refused if the record changed after your preview; preview again. There is no general edit or force-complete, and nothing marks identity verified or accepts terms for a participant. Cancelling an outbox email and sending a password reset cannot be undone.
    Why:
    Interventions must keep accepted terms and evidence intact and be traceable.
    If you need it done:
    Next actor: the participant who owns the step, or central operations, through /contact. Next action: route the request to them.
  • Workboard: you see and change only leads in your own place

    Allowed:
    Any staff role opens the workboard. Assigning, follow-ups and recording contact permission need a role that can edit: platform owner, central operations, managers and sales/BNI coordinators. Finance and QA reviewers can only read.
    Refused:
    Leads outside your place are not shown. A lead with no city, including every BNI introduction, needs a role with no place limit. You can only assign a lead to someone whose role covers it.
    Why:
    Leads hold personal contact details.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they set the city or pass the lead to someone who covers it.
  • A contact denial is one-way; only a platform owner covering that lead can reverse it

    Allowed:
    Anyone who can edit a lead records permission as granted or not granted, with a basis (up to 120 characters) and evidence (up to 500). Not granted moves the lead to suppressed. A platform owner whose own owner role covers the lead's city or area can reverse a denial with a reason (up to 300 characters); a lead with no city needs an owner role with no place limit. The reversal is recorded against the owner's account with the reason.
    Refused:
    Everyone else, including central operations and managers, cannot reverse a denial. An owner role for another city does not count, even with a manager role for the lead's city: platform owner (Mumbai) plus city manager (Raipur) cannot reverse a Raipur lead. Recording permission never sends a message.
    Why:
    A refusal to be contacted must stick.
    If you need it done:
    Next actor: a platform owner whose role covers the lead's place. Next action: they review the new evidence and record the reversal with it as the reason.
  • Do-not-contact (suppression) entries are add-only, except unverified /unsubscribe entries

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators add an email address with a reason (up to 500 characters); who added it is recorded. Recipients can add their own address on /unsubscribe; it takes effect at once and is recorded as an unverified entry. The same outreach staff may lift an unverified /unsubscribe entry with a reason (10 to 500 characters), for example when the owner of the address asks in writing to receive promotional email again. The lift records who lifted it, when, why and what the entry was. When outreach staff add an address that already has an unverified /unsubscribe entry, that entry becomes a permanent staff entry, recorded with who added it and why.
    Refused:
    Finance and QA reviewers and all restaurant, brand, printer and installer accounts cannot add or lift entries. Entries added by staff, and entries recorded before unverified entries were tracked, can never be lifted. A suppression and a lead's contact denial are separate: record both where both apply.
    Why:
    An opt-out must never be quietly reversed; only an entry nobody verified can be lifted, and only on the record.
    If you need it done:
    Next actor: one of the outreach staff named above. Next action: they add the address, or lift an unverified /unsubscribe entry with a reason (POST /api/suppressions/lift).
  • Inbound enquiry permission is specific; drafts, reminders and imports are not permission

    Allowed:
    Follow-ups, assignments, reminders and imports are internal records only.
    Refused:
    An enquiry submitted on /enquiry or the guided form records permission to respond to that enquiry, with source and timestamp; there is no separate opt-in. An existing denial, do-not-contact stage or suppressed address is not reopened by submission. The receipt is queued when an email is supplied, subject to identity and rate limits, and suppressed addresses cannot receive it. No feature sends promotional outreach email or WhatsApp. Imported leads start with permission unknown. BNI membership is not consent. Do not import scraped or gated-directory contacts. Decision: 5 October 2026.
    Why:
    A person's own submitted enquiry documents their request for an enquiry-specific reply, not promotional permission. Imports and drafts do not document that request.
    If you need it done:
    Next actor: the lead owner. Next action: check existing denial and suppression before responding to an inbound enquiry; for imported leads, record documented permission before one-to-one contact outside the platform.
  • Lead import: every row must be in a city you can edit

    Allowed:
    Paste CSV, preview, then commit. Only you can commit your preview, within 30 minutes.
    Refused:
    Rows in cities you cannot edit are left out (finance and QA reviewers cannot edit, so all their rows are left out). Duplicates are checked against all leads, including ones you cannot see. If your role changes between preview and commit, the commit is refused.
    Why:
    Import creates personal-data records under the same place rule as manual edits.
    If you need it done:
    Next actor: a colleague who covers the left-out rows, or central operations. Next action: give them only those rows.
  • Lead export: only some roles, only for their own place

    Allowed:
    Platform owner, central operations, managers and finance reviewers export leads for a city they cover. Exporting every city needs a role with no place limit.
    Refused:
    Sales/BNI coordinators and QA reviewers cannot export. "Export my leads" shows only leads you can export, which may be none.
    Why:
    Exporting copies personal data out of the platform.
    If you need it done:
    Next actor: your city manager or central operations. Next action: they run the export.
  • Assisted onboarding: recorded consent, operator invitation, owner acceptance

    Allowed:
    Platform owner and central operations anywhere; managers, sales/BNI coordinators and place-limited owner or operations roles in their own place. Record the consent channel, a statement of 12 to 500 characters and the owner's email.
    Refused:
    Suppressed, converted or dead leads; leads with unknown city for scoped roles; company or staff owner email. Cancellation is allowed only before owner acceptance and revokes the link, not mail already delivered.
    Why:
    Recorded consent, scoped staff access, a bound email-only invitation and owner-only acceptance protect the handover.
    If you need it done:
    Next actor: the restaurant owner. Next action: open the invitation, review the application and accept personally. Central operations resolves mail delivery failures.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Pictures: fixed limits and staff review

    Allowed:
    Up to 12 photos per venue location, 3 per display spot, and one logo plus one replacement waiting for review. Approved venue photos and logos are public; display spot photos stay internal.
    Refused:
    Rejected pictures count toward the limit until removed. Editing an approved picture's description takes it off the public page until reviewed again. Nobody reviews their own upload or a picture from their own organisation.
    Why:
    Public pictures must respect rights, consent and accuracy.
    If you need it done:
    Next actor: platform staff covering your city. Next action: they approve the picture or reject it with a reason.

Next actor and action: Next actor: the internal issuer for access gaps, or the assigned participant for a pending task. Next action: request a scoped grant or document the queue action.

Internal role

Area manager

area_manager

Follow up restaurants and coordinate jobs in explicitly assigned area(s); the title alone grants no city-wide access.

Start and setup

Accept an internal invitation and check the assigned area scope. An authenticator is optional (set one up at /account/security); only the platform owner must use one.

What to prepare

  • Internal membership and exact area grant
  • Assigned queue and permitted next action
  • Conflict-of-interest check for reviews

Who grants access

An authorized internal issuer grants this role and contained geography. Every list, detail and write rechecks scope.

Limits and gotchas

  • Do not infer authority from location address or a copied link.
  • You cannot independently approve your own payable work.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • A PutYourBrand staff account never joins, owns or accepts terms for a restaurant

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators may start an audited assisted onboarding and prepare steps the owner reviews. Finance and QA reviewers cannot.
    Refused:
    An account with any staff role, or a putyourbrand.in email address, cannot be added to a restaurant or accept its agreement, even if it also holds that restaurant's owner role.
    Why:
    Acceptance must come from the restaurant itself.
    If you need it done:
    Next actor: the restaurant owner, on an account with no staff role. Next action: they accept, or add their own non-staff person. Former staff ask central operations to end their staff roles first.
  • Staff roles: who may give which role, where

    Allowed:
    The platform owner, central operations and country, city and area managers give staff roles. Ranks: platform owner 100; central operations, QA reviewer, finance reviewer 90; country manager 60; city manager 40; area manager and sales/BNI coordinator 20. You may give a role of your rank or lower, for a place equal to or inside your own.
    Refused:
    A higher-ranked role; a wider place; a role with no place limit (unless you are platform owner or central operations with no limit); a role for yourself; a role for someone who is not a member of the platform organisation; an expiry that is not in the future. One of your roles must cover all of this by itself.
    Why:
    It stops a manager from choosing who reviews their own work, and stops authority growing beyond what was given.
    If you need it done:
    Next actor: an issuer of equal or higher rank who covers the place (a platform owner for platform owner roles). Next action: they give the role; the person must have accepted a platform invitation first.
  • Staff roles: ending a role takes effect at once, within your rank and place

    Allowed:
    An issuer may end a staff role of equal or lower rank inside their own place. It stops on the holder's next action and is audited with who ended which role and when.
    Refused:
    Ending your own role; ending a higher-ranked role (central operations cannot end a platform owner role); ending a role with no place limit, or outside your place, unless you are platform owner or central operations with no limit.
    Why:
    Roles must be removable quickly, but only by someone who could have given them.
    If you need it done:
    Next actor: central operations (a platform owner for platform owner roles). Next action: they end the role on the Team page.
  • Admin is for the platform owner, central operations and country, city and area managers

    Allowed:
    Those roles open /admin. A manager limited to a place sees and acts on records in that place only.
    Refused:
    Sales/BNI coordinators, finance and QA reviewers and all restaurant, brand, printer and installer accounts. The mail outbox and stuck drafts need a role with no place limit. Password resets and restaurant owner recovery need the platform owner or central operations with no place limit. Restaurant setups with no known city are hidden from managers limited to a place.
    Why:
    Admin changes other people's records, so it is limited to operational roles and their place.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they make the change, or you ask an issuer for the role you need.
  • Admin interventions are named, previewed, reasoned and audited

    Allowed:
    Eight named intervention kinds. Each shows a preview of the current record; you confirm it with a reason code and a reason of 8 to 2,000 characters. Other staff actions (owner recovery, assisted onboarding approvals, staff roles) are separately audited with their own reason rules.
    Refused:
    A confirmation is refused if the record changed after your preview; preview again. There is no general edit or force-complete, and nothing marks identity verified or accepts terms for a participant. Cancelling an outbox email and sending a password reset cannot be undone.
    Why:
    Interventions must keep accepted terms and evidence intact and be traceable.
    If you need it done:
    Next actor: the participant who owns the step, or central operations, through /contact. Next action: route the request to them.
  • Workboard: you see and change only leads in your own place

    Allowed:
    Any staff role opens the workboard. Assigning, follow-ups and recording contact permission need a role that can edit: platform owner, central operations, managers and sales/BNI coordinators. Finance and QA reviewers can only read.
    Refused:
    Leads outside your place are not shown. A lead with no city, including every BNI introduction, needs a role with no place limit. You can only assign a lead to someone whose role covers it.
    Why:
    Leads hold personal contact details.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they set the city or pass the lead to someone who covers it.
  • A contact denial is one-way; only a platform owner covering that lead can reverse it

    Allowed:
    Anyone who can edit a lead records permission as granted or not granted, with a basis (up to 120 characters) and evidence (up to 500). Not granted moves the lead to suppressed. A platform owner whose own owner role covers the lead's city or area can reverse a denial with a reason (up to 300 characters); a lead with no city needs an owner role with no place limit. The reversal is recorded against the owner's account with the reason.
    Refused:
    Everyone else, including central operations and managers, cannot reverse a denial. An owner role for another city does not count, even with a manager role for the lead's city: platform owner (Mumbai) plus city manager (Raipur) cannot reverse a Raipur lead. Recording permission never sends a message.
    Why:
    A refusal to be contacted must stick.
    If you need it done:
    Next actor: a platform owner whose role covers the lead's place. Next action: they review the new evidence and record the reversal with it as the reason.
  • Do-not-contact (suppression) entries are add-only, except unverified /unsubscribe entries

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators add an email address with a reason (up to 500 characters); who added it is recorded. Recipients can add their own address on /unsubscribe; it takes effect at once and is recorded as an unverified entry. The same outreach staff may lift an unverified /unsubscribe entry with a reason (10 to 500 characters), for example when the owner of the address asks in writing to receive promotional email again. The lift records who lifted it, when, why and what the entry was. When outreach staff add an address that already has an unverified /unsubscribe entry, that entry becomes a permanent staff entry, recorded with who added it and why.
    Refused:
    Finance and QA reviewers and all restaurant, brand, printer and installer accounts cannot add or lift entries. Entries added by staff, and entries recorded before unverified entries were tracked, can never be lifted. A suppression and a lead's contact denial are separate: record both where both apply.
    Why:
    An opt-out must never be quietly reversed; only an entry nobody verified can be lifted, and only on the record.
    If you need it done:
    Next actor: one of the outreach staff named above. Next action: they add the address, or lift an unverified /unsubscribe entry with a reason (POST /api/suppressions/lift).
  • Inbound enquiry permission is specific; drafts, reminders and imports are not permission

    Allowed:
    Follow-ups, assignments, reminders and imports are internal records only.
    Refused:
    An enquiry submitted on /enquiry or the guided form records permission to respond to that enquiry, with source and timestamp; there is no separate opt-in. An existing denial, do-not-contact stage or suppressed address is not reopened by submission. The receipt is queued when an email is supplied, subject to identity and rate limits, and suppressed addresses cannot receive it. No feature sends promotional outreach email or WhatsApp. Imported leads start with permission unknown. BNI membership is not consent. Do not import scraped or gated-directory contacts. Decision: 5 October 2026.
    Why:
    A person's own submitted enquiry documents their request for an enquiry-specific reply, not promotional permission. Imports and drafts do not document that request.
    If you need it done:
    Next actor: the lead owner. Next action: check existing denial and suppression before responding to an inbound enquiry; for imported leads, record documented permission before one-to-one contact outside the platform.
  • Lead import: every row must be in a city you can edit

    Allowed:
    Paste CSV, preview, then commit. Only you can commit your preview, within 30 minutes.
    Refused:
    Rows in cities you cannot edit are left out (finance and QA reviewers cannot edit, so all their rows are left out). Duplicates are checked against all leads, including ones you cannot see. If your role changes between preview and commit, the commit is refused.
    Why:
    Import creates personal-data records under the same place rule as manual edits.
    If you need it done:
    Next actor: a colleague who covers the left-out rows, or central operations. Next action: give them only those rows.
  • Lead export: only some roles, only for their own place

    Allowed:
    Platform owner, central operations, managers and finance reviewers export leads for a city they cover. Exporting every city needs a role with no place limit.
    Refused:
    Sales/BNI coordinators and QA reviewers cannot export. "Export my leads" shows only leads you can export, which may be none.
    Why:
    Exporting copies personal data out of the platform.
    If you need it done:
    Next actor: your city manager or central operations. Next action: they run the export.
  • Assisted onboarding: recorded consent, operator invitation, owner acceptance

    Allowed:
    Platform owner and central operations anywhere; managers, sales/BNI coordinators and place-limited owner or operations roles in their own place. Record the consent channel, a statement of 12 to 500 characters and the owner's email.
    Refused:
    Suppressed, converted or dead leads; leads with unknown city for scoped roles; company or staff owner email. Cancellation is allowed only before owner acceptance and revokes the link, not mail already delivered.
    Why:
    Recorded consent, scoped staff access, a bound email-only invitation and owner-only acceptance protect the handover.
    If you need it done:
    Next actor: the restaurant owner. Next action: open the invitation, review the application and accept personally. Central operations resolves mail delivery failures.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Pictures: fixed limits and staff review

    Allowed:
    Up to 12 photos per venue location, 3 per display spot, and one logo plus one replacement waiting for review. Approved venue photos and logos are public; display spot photos stay internal.
    Refused:
    Rejected pictures count toward the limit until removed. Editing an approved picture's description takes it off the public page until reviewed again. Nobody reviews their own upload or a picture from their own organisation.
    Why:
    Public pictures must respect rights, consent and accuracy.
    If you need it done:
    Next actor: platform staff covering your city. Next action: they approve the picture or reject it with a reason.

Next actor and action: Next actor: internal issuer for scope changes, or the named participant for an outstanding step. Next action: request the exact area or record the follow-up.

Internal role

Sales / BNI coordinator

sales_bni_coordinator

Manage assigned prospects, introductions and follow-ups; no automatic contact, unrestricted export, or assumed referral fee.

Start and setup

Accept an internal invitation and sign in with your password. An authenticator is optional (set one up at /account/security); only the platform owner must use one.

What to prepare

  • Active internal grant and assigned geography
  • Documented contact permission before any contact
  • Next follow-up and responsible actor

Who grants access

An authorized internal issuer grants access. A role grant is not permission to contact any person; consent/suppression and contact policies still apply.

Limits and gotchas

  • The /admin surface is limited to platform owner, central operations, and country/city/area manager roles; a coordinator grant does not admit you there.
  • Drafts and reminders do not authorize sending.
  • Do not use directory scraping, bulk outreach, or assume referral compensation.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • A PutYourBrand staff account never joins, owns or accepts terms for a restaurant

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators may start an audited assisted onboarding and prepare steps the owner reviews. Finance and QA reviewers cannot.
    Refused:
    An account with any staff role, or a putyourbrand.in email address, cannot be added to a restaurant or accept its agreement, even if it also holds that restaurant's owner role.
    Why:
    Acceptance must come from the restaurant itself.
    If you need it done:
    Next actor: the restaurant owner, on an account with no staff role. Next action: they accept, or add their own non-staff person. Former staff ask central operations to end their staff roles first.
  • Staff roles: who may give which role, where

    Allowed:
    The platform owner, central operations and country, city and area managers give staff roles. Ranks: platform owner 100; central operations, QA reviewer, finance reviewer 90; country manager 60; city manager 40; area manager and sales/BNI coordinator 20. You may give a role of your rank or lower, for a place equal to or inside your own.
    Refused:
    A higher-ranked role; a wider place; a role with no place limit (unless you are platform owner or central operations with no limit); a role for yourself; a role for someone who is not a member of the platform organisation; an expiry that is not in the future. One of your roles must cover all of this by itself.
    Why:
    It stops a manager from choosing who reviews their own work, and stops authority growing beyond what was given.
    If you need it done:
    Next actor: an issuer of equal or higher rank who covers the place (a platform owner for platform owner roles). Next action: they give the role; the person must have accepted a platform invitation first.
  • Staff roles: ending a role takes effect at once, within your rank and place

    Allowed:
    An issuer may end a staff role of equal or lower rank inside their own place. It stops on the holder's next action and is audited with who ended which role and when.
    Refused:
    Ending your own role; ending a higher-ranked role (central operations cannot end a platform owner role); ending a role with no place limit, or outside your place, unless you are platform owner or central operations with no limit.
    Why:
    Roles must be removable quickly, but only by someone who could have given them.
    If you need it done:
    Next actor: central operations (a platform owner for platform owner roles). Next action: they end the role on the Team page.
  • Admin is for the platform owner, central operations and country, city and area managers

    Allowed:
    Those roles open /admin. A manager limited to a place sees and acts on records in that place only.
    Refused:
    Sales/BNI coordinators, finance and QA reviewers and all restaurant, brand, printer and installer accounts. The mail outbox and stuck drafts need a role with no place limit. Password resets and restaurant owner recovery need the platform owner or central operations with no place limit. Restaurant setups with no known city are hidden from managers limited to a place.
    Why:
    Admin changes other people's records, so it is limited to operational roles and their place.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they make the change, or you ask an issuer for the role you need.
  • Workboard: you see and change only leads in your own place

    Allowed:
    Any staff role opens the workboard. Assigning, follow-ups and recording contact permission need a role that can edit: platform owner, central operations, managers and sales/BNI coordinators. Finance and QA reviewers can only read.
    Refused:
    Leads outside your place are not shown. A lead with no city, including every BNI introduction, needs a role with no place limit. You can only assign a lead to someone whose role covers it.
    Why:
    Leads hold personal contact details.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they set the city or pass the lead to someone who covers it.
  • A contact denial is one-way; only a platform owner covering that lead can reverse it

    Allowed:
    Anyone who can edit a lead records permission as granted or not granted, with a basis (up to 120 characters) and evidence (up to 500). Not granted moves the lead to suppressed. A platform owner whose own owner role covers the lead's city or area can reverse a denial with a reason (up to 300 characters); a lead with no city needs an owner role with no place limit. The reversal is recorded against the owner's account with the reason.
    Refused:
    Everyone else, including central operations and managers, cannot reverse a denial. An owner role for another city does not count, even with a manager role for the lead's city: platform owner (Mumbai) plus city manager (Raipur) cannot reverse a Raipur lead. Recording permission never sends a message.
    Why:
    A refusal to be contacted must stick.
    If you need it done:
    Next actor: a platform owner whose role covers the lead's place. Next action: they review the new evidence and record the reversal with it as the reason.
  • Do-not-contact (suppression) entries are add-only, except unverified /unsubscribe entries

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators add an email address with a reason (up to 500 characters); who added it is recorded. Recipients can add their own address on /unsubscribe; it takes effect at once and is recorded as an unverified entry. The same outreach staff may lift an unverified /unsubscribe entry with a reason (10 to 500 characters), for example when the owner of the address asks in writing to receive promotional email again. The lift records who lifted it, when, why and what the entry was. When outreach staff add an address that already has an unverified /unsubscribe entry, that entry becomes a permanent staff entry, recorded with who added it and why.
    Refused:
    Finance and QA reviewers and all restaurant, brand, printer and installer accounts cannot add or lift entries. Entries added by staff, and entries recorded before unverified entries were tracked, can never be lifted. A suppression and a lead's contact denial are separate: record both where both apply.
    Why:
    An opt-out must never be quietly reversed; only an entry nobody verified can be lifted, and only on the record.
    If you need it done:
    Next actor: one of the outreach staff named above. Next action: they add the address, or lift an unverified /unsubscribe entry with a reason (POST /api/suppressions/lift).
  • Inbound enquiry permission is specific; drafts, reminders and imports are not permission

    Allowed:
    Follow-ups, assignments, reminders and imports are internal records only.
    Refused:
    An enquiry submitted on /enquiry or the guided form records permission to respond to that enquiry, with source and timestamp; there is no separate opt-in. An existing denial, do-not-contact stage or suppressed address is not reopened by submission. The receipt is queued when an email is supplied, subject to identity and rate limits, and suppressed addresses cannot receive it. No feature sends promotional outreach email or WhatsApp. Imported leads start with permission unknown. BNI membership is not consent. Do not import scraped or gated-directory contacts. Decision: 5 October 2026.
    Why:
    A person's own submitted enquiry documents their request for an enquiry-specific reply, not promotional permission. Imports and drafts do not document that request.
    If you need it done:
    Next actor: the lead owner. Next action: check existing denial and suppression before responding to an inbound enquiry; for imported leads, record documented permission before one-to-one contact outside the platform.
  • Lead import: every row must be in a city you can edit

    Allowed:
    Paste CSV, preview, then commit. Only you can commit your preview, within 30 minutes.
    Refused:
    Rows in cities you cannot edit are left out (finance and QA reviewers cannot edit, so all their rows are left out). Duplicates are checked against all leads, including ones you cannot see. If your role changes between preview and commit, the commit is refused.
    Why:
    Import creates personal-data records under the same place rule as manual edits.
    If you need it done:
    Next actor: a colleague who covers the left-out rows, or central operations. Next action: give them only those rows.
  • Lead export: only some roles, only for their own place

    Allowed:
    Platform owner, central operations, managers and finance reviewers export leads for a city they cover. Exporting every city needs a role with no place limit.
    Refused:
    Sales/BNI coordinators and QA reviewers cannot export. "Export my leads" shows only leads you can export, which may be none.
    Why:
    Exporting copies personal data out of the platform.
    If you need it done:
    Next actor: your city manager or central operations. Next action: they run the export.
  • Assisted onboarding: recorded consent, operator invitation, owner acceptance

    Allowed:
    Platform owner and central operations anywhere; managers, sales/BNI coordinators and place-limited owner or operations roles in their own place. Record the consent channel, a statement of 12 to 500 characters and the owner's email.
    Refused:
    Suppressed, converted or dead leads; leads with unknown city for scoped roles; company or staff owner email. Cancellation is allowed only before owner acceptance and revokes the link, not mail already delivered.
    Why:
    Recorded consent, scoped staff access, a bound email-only invitation and owner-only acceptance protect the handover.
    If you need it done:
    Next actor: the restaurant owner. Next action: open the invitation, review the application and accept personally. Central operations resolves mail delivery failures.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.

Next actor and action: Next actor: the prospect/contact or assigned operations reviewer. Next action: verify permission and record a permitted, human-approved follow-up.

Application identifier

Installer application (not a current invited workspace role)

installer

Application-flow identifier for installer interest and qualification; it is not one of the current team invitation roles.

Start and setup

Use the public installer application to submit your own details and resume only through its secure progress link.

What to prepare

  • Applicant contact channel
  • Skills and service areas requested by the form
  • Eligibility details requested at the current step

Who grants access

No role grant is created by reading Docs or applying. Qualification and job access require the applicable reviewed workflow and organisation grant.

Limits and gotchas

  • Application is not approval, an employment offer, a job assignment, or a promise of earnings.
  • Do not share secure resume links; there may be no eligible work available.

Rules and limits you should know before you start

  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Installers: applying is not approval or a job offer

    Allowed:
    An application creates your installer record. Central operations or the platform owner review it; qualification is given only from under review. Offers go only to installers who are qualified, have a skill, serve the job's city and have a current training record.
    Refused:
    A staff member who belongs to your organisation cannot qualify it. A qualified installer can be moved to not qualified or inactive; inactive goes back through review. No job, number of jobs or earnings is promised.
    Why:
    Work goes only to reviewed, eligible installers.
    If you need it done:
    Next actor: central operations. Next action: review your application; follow the progress page's current request.

Next actor and action: Next actor: the applicant for requested information, then the review team. Next action: follow the progress page's current request; do not treat an application as job access.

Application identifier

Printer application (not a current invited workspace role)

printer

Application-flow identifier for printer interest; the current invited workspace roles are printer_owner and printer_operator.

Start and setup

Review the public print-partner information and submit an enquiry; wait for an approved organisation invitation before using the portal.

What to prepare

  • Business and service coverage requested by the enquiry
  • Print capabilities and current contact details
  • No credentials or bank details in an enquiry

Who grants access

An enquiry creates no printer account or access. An authorized organisation owner/staff issuer must create an invitation through the supported flow.

Limits and gotchas

  • An RFQ is a request for a quote, not an order; no volume is guaranteed.
  • Do not treat this legacy role ID as an invitation option.

Rules and limits you should know before you start

  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Printers: applying is not approval; matching uses your current profile

    Allowed:
    A signed-in account registers a printer organisation; it starts pending until central operations or the platform owner approve it. Approved printers are matched on their current service cities and capabilities; later edits apply straight away without a new review. Matching can also suggest printers in nearby cities.
    Refused:
    Your home city counts only if it is in your service cities. A staff member who belongs to your organisation cannot approve it. Only an active printer owner with no staff role makes someone a co-owner (central operations only while the printer has no owner); only central operations ends the printer owner role. You cannot remove your own membership. A printer or brand role never allows running a match.
    Why:
    Keep your profile accurate: requests are matched on what it says.
    If you need it done:
    Next actor: central operations. Next action: review your printer organisation, or answer questions about your profile.

Next actor and action: Next actor: the printer applicant, then authorized onboarding staff. Next action: submit an enquiry and wait for a reviewed invitation if eligible.

Participant role

Restaurant owner

restaurant_owner

Own a restaurant organisation, manage its membership and perform owner-authorized commercial actions.

Start and setup

Start from the restaurant information/enquiry path or accept an organisation invitation; membership and binding agreement actions do not need an authenticator. An authenticator is optional (set one up at /account/security); only the platform owner must use one.

What to prepare

  • Legal/business and contact details requested by the form
  • Location identity and geography
  • Current approved terms and authorized signer
  • Separate diner offer vs venue baseline advertiser offer

Who grants access

The restaurant owner is the authorized participant for owner-only membership and binding actions; the server checks organisation, role and scope. No authenticator code is required for membership or binding actions; only the platform owner must use an authenticator. The internal `/dashboard/team` staff-invitation screen is not a restaurant workspace. Only an existing owner of the same restaurant can invite or grant another restaurant owner; PutYourBrand staff cannot, and an account that holds any active PutYourBrand staff role cannot accept the step 5 agreement even if it also owns the restaurant.

Limits and gotchas

  • INR 800/table is an onboarding reference, not complete commercial terms.
  • No checkout or automated payment; reservation is not a guarantee of installation or footfall.
  • Wizard step 4 lists activatable diner offers, not the venue's baseline advertiser offer.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • A PutYourBrand staff account never joins, owns or accepts terms for a restaurant

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators may start an audited assisted onboarding and prepare steps the owner reviews. Finance and QA reviewers cannot.
    Refused:
    An account with any staff role, or a putyourbrand.in email address, cannot be added to a restaurant or accept its agreement, even if it also holds that restaurant's owner role.
    Why:
    Acceptance must come from the restaurant itself.
    If you need it done:
    Next actor: the restaurant owner, on an account with no staff role. Next action: they accept, or add their own non-staff person. Former staff ask central operations to end their staff roles first.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Restaurant team: the owner and trusted team members manage people

    Allowed:
    On the Team page an owner invites co-owners, operators and managers by email and removes operators and managers. Operators and managers whose role covers the whole restaurant (everyone who joined by a Team invitation) can also add members and give or remove operator and manager roles; this is intended, so invite only people you trust. A central operations or platform owner role with no place limit can remove people (end a membership, take away an operator or manager role) without a request from the restaurant. Every change is recorded.
    Refused:
    PutYourBrand staff cannot add anyone to a restaurant team or give anyone an operator, manager or owner role, because anyone on a restaurant team can accept offers that bind the restaurant. This includes an owner, operator or manager whose account also holds a staff role. Two separately audited exceptions exist, and in both the owner accepts the invitation themselves: the first owner invitation of an assisted onboarding (only for a restaurant that never had an owner, at the eligible operator's audited start) and an approved two-person owner recovery (only when the restaurant has no active owner). Only an existing owner can make someone an owner, and ending an owner's role or membership needs a central operations or platform owner role with no place limit. Nobody can remove themselves. Removing someone ends every role they held in the restaurant; inviting them again gives only the role in the new invitation. Someone who already has access cannot be invited again: remove and re-invite to change a role. Staff accounts and putyourbrand.in addresses cannot be added. A role from a Team invitation covers every location of the restaurant. An owner whose account also holds a staff role sees no invite form on the Team page; the page names who can invite instead: another owner with no staff role, or an operator or manager covering the whole restaurant (existing accounts, operator or manager roles only), and failing both, central operations ending that owner's staff role. Owner recovery and assisted onboarding do not apply while the restaurant has an owner.
    Why:
    Who acts for a restaurant is the restaurant's decision, run as a trusted team; staff never accept terms for a restaurant, so staff never put someone on its team.
    If you need it done:
    Next actor: an owner of this restaurant, or central operations, through /contact for owner changes. Next action: they make the change.
  • Restaurant setup: steps go in order, and only a restaurant owner accepts

    Allowed:
    Steps 1 to 4 go in order and can be revisited. Step 1 is completed by the person the setup belongs to (who started it or holds its resume link) and makes them owner.
    Refused:
    Skipping steps. Step 5 (accept) is for a restaurant owner with no staff role; operators, managers and staff can review but not accept. If anything changed since you reviewed, reload Review and fees first. Acceptance is final and keeps a fixed record of the terms.
    Why:
    Acceptance binds the restaurant.
    If you need it done:
    Next actor: a restaurant owner. Next action: reload Review and fees if asked, then accept.
  • Venue offers and baseline packages: owner approval, and approved means fixed

    Allowed:
    Any venue member drafts a baseline package or diner offer. The restaurant owner or central operations approves it. A baseline package needs its amount, payer and tax set and an average-bill answer; a diner offer needs a real amount. An owner may approve content they wrote.
    Refused:
    Operators and managers cannot approve. A staff member who prepared it, or a non-owner who wrote it, cannot approve it. Approved or retired packages and offers cannot be edited: create a new one. Pay-per-sale packages are refused.
    Why:
    Brands make offers on the approved package, so it must not change under them.
    If you need it done:
    Next actor: the restaurant owner or central operations. Next action: approve the draft, or create a replacement.
  • Sellable periods: offering one reserves nothing, and sold periods stay

    Allowed:
    Venue members open sellable periods (whole IST days) on active tables and display spots, and retire periods nobody has bid on or bought.
    Refused:
    Side B of a display ("Place your ad here") is never sold. A period with an agreement or an open offer cannot be retired, nor can its table or spot. Retiring is final. A period on sale promises no buyer, footfall or installation.
    Why:
    A brand that bought or is negotiating relies on the period.
    If you need it done:
    Next actor: the venue team. Next action: let an open offer expire or accept it (a counter keeps it open); to free a sold period, an owner of either side cancels the agreement first.
  • Exports are owner-only; the logo can be changed by the wider team

    Allowed:
    Owners export their organisation's data. Anyone whose role covers the whole organisation can change its logo; staff review a new logo before it is public.
    Refused:
    Operators, managers and workers cannot export (for example the tables CSV or QR analytics CSV).
    Why:
    Exporting copies data out of the platform.
    If you need it done:
    Next actor: an owner of your organisation. Next action: they run the export.
  • Pictures: fixed limits and staff review

    Allowed:
    Up to 12 photos per venue location, 3 per display spot, and one logo plus one replacement waiting for review. Approved venue photos and logos are public; display spot photos stay internal.
    Refused:
    Rejected pictures count toward the limit until removed. Editing an approved picture's description takes it off the public page until reviewed again. Nobody reviews their own upload or a picture from their own organisation.
    Why:
    Public pictures must respect rights, consent and accuracy.
    If you need it done:
    Next actor: platform staff covering your city. Next action: they approve the picture or reject it with a reason.
  • Offers: sides take turns, nothing is accepted automatically, and any member of a side can accept

    Allowed:
    A brand member makes a private offer on an approved package. Sides counter in turn. The side that did not propose the latest terms accepts that exact latest version. Any member of that side can accept, including restaurant operators and managers and brand operators.
    Refused:
    Accepting an older version, your own side's terms, or an offer after its expiry (end of the chosen IST day). Countering out of turn. Only the side that proposed the latest terms can withdraw them, and that is final. There is no decline button: counter, or let it expire. An acceptance binds your organisation, so agree internally who accepts.
    Why:
    Each acceptance must answer terms the other side proposed.
    If you need it done:
    Next actor: the side shown as next on the offer. Next action: counter, accept or let it expire; after expiry make a fresh offer.
  • Accepting creates the agreement and reserves the period in one step

    Allowed:
    On acceptance the agreement and the reservation are saved together or not at all. Terms that match the package start active; different terms wait for reapproval.
    Refused:
    A fully reserved period cannot be accepted. An open offer reserves nothing. Different terms are reapproved only by the restaurant owner or central operations with no tie to the brand. A reservation does not promise printing, installation, footfall or sales.
    Why:
    A period is never sold twice.
    If you need it done:
    Next actor: the restaurant owner or central operations. Next action: reapprove or cancel; for a full period, offer another one.
  • Agreements: terms are fixed; change them by amendment or owner cancellation

    Allowed:
    Any party member proposes one amendment at a time; a member of the other party accepts it; the proposing side can withdraw it. An owner of either party can cancel an active agreement alone, which frees the period.
    Refused:
    Operators and managers cannot cancel. An expired agreement cannot be cancelled. Cancelling is final. Accepted terms are never rewritten. A side cannot accept its own amendment. A member of both parties' organisations is refused on both sides.
    Why:
    Accepted terms are the record; changing them needs the other side.
    If you need it done:
    Next actor: the other party to accept an amendment, the proposing party to withdraw it, or an owner to cancel. Next action: as stated on the agreement.
  • Artwork: the brand uploads, an owner decides the proof, and approval fixes it

    Allowed:
    Brand members upload artwork (PNG, JPEG or PDF, up to 25 MB) while the agreement is active. Any party member generates the proof. The brand owner or restaurant owner approves or rejects it (a rejection needs a reason).
    Refused:
    Restaurant members cannot upload artwork. Operators and managers cannot decide a proof. Only approved artwork is printed and an approved version cannot change. Staff cannot download artwork files.
    Why:
    What is printed must be exactly what an owner approved.
    If you need it done:
    Next actor: the brand (upload) or an owner of either party (decision). Next action: upload a new version or decide the proof.
  • A placement goes live only when all seven steps are done

    Allowed:
    The restaurant owner, brand owner or a platform operator activates once there are approved terms, an approved proof, a confirmed print order, a completed installation, the venue sign-off, independent QA and a recorded settlement of the installer's earning.
    Refused:
    Operators and managers cannot activate. A staff waiver blocks a step rather than completing it. Activation is final; pausing is the only reverse, and resuming re-checks every step.
    Why:
    Going live is where every earlier step must be shown.
    If you need it done:
    Next actor: whoever owns the first missing step, named on the activation panel. Next action: complete it, then retry.
  • A print request is not an order

    Allowed:
    The brand or restaurant on an active agreement with an approved proof asks for quotes; printers covering that city are invited. An invited printer quotes or declines with a reason; a new quote replaces its earlier one. Any member of either side can choose a quote, which creates the order; the printer then confirms it.
    Refused:
    Nothing becomes an order by itself. Staff cannot quote for a printer. An expired quote, or one above the budget, cannot be chosen. Choosing is final. Printers see the requester's budget. Do not buy stock or print before your order is confirmed.
    Why:
    No volume is promised to any printer, and no requester is bound until they choose.
    If you need it done:
    Next actor: the requester (choose) or the chosen printer (confirm). Next action: choose a valid quote, or confirm the order.
  • The printer records delivery; settlement follows a complete, undamaged delivery

    Allowed:
    The chosen printer records dispatch and delivery, including the count and any damage.
    Refused:
    A damaged delivery asks for a replacement of the whole ordered quantity. Settlement waits for a complete, undamaged delivery and is recorded by central operations; whoever recorded the delivery cannot record its settlement.
    Why:
    Payment follows evidence, recorded by a different person.
    If you need it done:
    Next actor: the printer (replacement) or central operations (settlement). Next action: send the replacement, or record the settlement once paid.
  • Installation jobs: the venue owner controls the job; one installer wins

    Allowed:
    The restaurant owner or central operations creates a job on an active agreement; pay is fixed when created. A venue member offers it to eligible installers; one installer organisation accepts. The installer proposes a time and the restaurant owner confirms it.
    Refused:
    Operators and managers cannot create, confirm, cancel or reopen jobs. A job with no rate cannot be offered. Work cannot start before the venue confirms the time. The restaurant owner can cancel a job that is not completed, with a reason, even after evidence was sent; a cancelled job pays nothing.
    Why:
    The venue hosts the work and decides who comes and when.
    If you need it done:
    Next actor: the restaurant owner (create, confirm, cancel) or the offered installer (accept). Next action: as shown on the job.
  • Evidence: the installer sends it, the restaurant owner acknowledges, someone else decides QA

    Allowed:
    The accepting installer sends 1 to 20 PNG or JPEG photos (up to 10 MB each). The sign-off link is shown once to the installer, who gives it to the restaurant. The restaurant owner (or central operations or the platform owner) acknowledges through it. QA review follows.
    Refused:
    Restaurant operators and managers cannot acknowledge. Keep the sign-off link: it is not shown again. The person who acknowledged cannot also make the QA decision. One dispute at a time per job; only central operations or the platform owner resolve it, and never the person who made the job's QA decision or gave its venue acknowledgement.
    Why:
    Payable work needs two different people to confirm it.
    If you need it done:
    Next actor: the restaurant owner, then an independent QA reviewer. Next action: acknowledge from the link, then QA decides.

Next actor and action: Next actor: the restaurant owner for setup/acceptance; the venue owner, platform owner, or central operations for diner-offer approval; the brand owner and platform reviewer for campaign approval. Next action: use only an available authorized control; step 4 cannot proceed without an active campaign and approved diner offer.

Participant role

Restaurant operator

restaurant_operator

Work for the one restaurant organisation your grant names; no access to another restaurant by guessing an ID. A role received by accepting a Team invitation currently covers every location of that restaurant.

Start and setup

Accept a restaurant organisation invitation and verify which location(s) your grant covers.

What to prepare

  • Active organisation membership and location scope
  • Accurate venue information and requested evidence
  • Escalation contact for commercial terms

Who grants access

The restaurant owner or authorized staff issuer invites/grants access; server-side membership and geographic checks decide each page/action.

Limits and gotchas

  • Step 1 creates the restaurant organisation and grants restaurant_owner to the person bound to the wizard by creator or resume-token proof; a staff-only wizard has no such participant and cannot create owner authority. This binding is not independent legal identity verification.
  • Do not accept terms or attest for another participant.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Restaurant team: the owner and trusted team members manage people

    Allowed:
    On the Team page an owner invites co-owners, operators and managers by email and removes operators and managers. Operators and managers whose role covers the whole restaurant (everyone who joined by a Team invitation) can also add members and give or remove operator and manager roles; this is intended, so invite only people you trust. A central operations or platform owner role with no place limit can remove people (end a membership, take away an operator or manager role) without a request from the restaurant. Every change is recorded.
    Refused:
    PutYourBrand staff cannot add anyone to a restaurant team or give anyone an operator, manager or owner role, because anyone on a restaurant team can accept offers that bind the restaurant. This includes an owner, operator or manager whose account also holds a staff role. Two separately audited exceptions exist, and in both the owner accepts the invitation themselves: the first owner invitation of an assisted onboarding (only for a restaurant that never had an owner, at the eligible operator's audited start) and an approved two-person owner recovery (only when the restaurant has no active owner). Only an existing owner can make someone an owner, and ending an owner's role or membership needs a central operations or platform owner role with no place limit. Nobody can remove themselves. Removing someone ends every role they held in the restaurant; inviting them again gives only the role in the new invitation. Someone who already has access cannot be invited again: remove and re-invite to change a role. Staff accounts and putyourbrand.in addresses cannot be added. A role from a Team invitation covers every location of the restaurant. An owner whose account also holds a staff role sees no invite form on the Team page; the page names who can invite instead: another owner with no staff role, or an operator or manager covering the whole restaurant (existing accounts, operator or manager roles only), and failing both, central operations ending that owner's staff role. Owner recovery and assisted onboarding do not apply while the restaurant has an owner.
    Why:
    Who acts for a restaurant is the restaurant's decision, run as a trusted team; staff never accept terms for a restaurant, so staff never put someone on its team.
    If you need it done:
    Next actor: an owner of this restaurant, or central operations, through /contact for owner changes. Next action: they make the change.
  • Restaurant setup: steps go in order, and only a restaurant owner accepts

    Allowed:
    Steps 1 to 4 go in order and can be revisited. Step 1 is completed by the person the setup belongs to (who started it or holds its resume link) and makes them owner.
    Refused:
    Skipping steps. Step 5 (accept) is for a restaurant owner with no staff role; operators, managers and staff can review but not accept. If anything changed since you reviewed, reload Review and fees first. Acceptance is final and keeps a fixed record of the terms.
    Why:
    Acceptance binds the restaurant.
    If you need it done:
    Next actor: a restaurant owner. Next action: reload Review and fees if asked, then accept.
  • Venue offers and baseline packages: owner approval, and approved means fixed

    Allowed:
    Any venue member drafts a baseline package or diner offer. The restaurant owner or central operations approves it. A baseline package needs its amount, payer and tax set and an average-bill answer; a diner offer needs a real amount. An owner may approve content they wrote.
    Refused:
    Operators and managers cannot approve. A staff member who prepared it, or a non-owner who wrote it, cannot approve it. Approved or retired packages and offers cannot be edited: create a new one. Pay-per-sale packages are refused.
    Why:
    Brands make offers on the approved package, so it must not change under them.
    If you need it done:
    Next actor: the restaurant owner or central operations. Next action: approve the draft, or create a replacement.
  • Sellable periods: offering one reserves nothing, and sold periods stay

    Allowed:
    Venue members open sellable periods (whole IST days) on active tables and display spots, and retire periods nobody has bid on or bought.
    Refused:
    Side B of a display ("Place your ad here") is never sold. A period with an agreement or an open offer cannot be retired, nor can its table or spot. Retiring is final. A period on sale promises no buyer, footfall or installation.
    Why:
    A brand that bought or is negotiating relies on the period.
    If you need it done:
    Next actor: the venue team. Next action: let an open offer expire or accept it (a counter keeps it open); to free a sold period, an owner of either side cancels the agreement first.
  • Exports are owner-only; the logo can be changed by the wider team

    Allowed:
    Owners export their organisation's data. Anyone whose role covers the whole organisation can change its logo; staff review a new logo before it is public.
    Refused:
    Operators, managers and workers cannot export (for example the tables CSV or QR analytics CSV).
    Why:
    Exporting copies data out of the platform.
    If you need it done:
    Next actor: an owner of your organisation. Next action: they run the export.
  • Pictures: fixed limits and staff review

    Allowed:
    Up to 12 photos per venue location, 3 per display spot, and one logo plus one replacement waiting for review. Approved venue photos and logos are public; display spot photos stay internal.
    Refused:
    Rejected pictures count toward the limit until removed. Editing an approved picture's description takes it off the public page until reviewed again. Nobody reviews their own upload or a picture from their own organisation.
    Why:
    Public pictures must respect rights, consent and accuracy.
    If you need it done:
    Next actor: platform staff covering your city. Next action: they approve the picture or reject it with a reason.
  • Offers: sides take turns, nothing is accepted automatically, and any member of a side can accept

    Allowed:
    A brand member makes a private offer on an approved package. Sides counter in turn. The side that did not propose the latest terms accepts that exact latest version. Any member of that side can accept, including restaurant operators and managers and brand operators.
    Refused:
    Accepting an older version, your own side's terms, or an offer after its expiry (end of the chosen IST day). Countering out of turn. Only the side that proposed the latest terms can withdraw them, and that is final. There is no decline button: counter, or let it expire. An acceptance binds your organisation, so agree internally who accepts.
    Why:
    Each acceptance must answer terms the other side proposed.
    If you need it done:
    Next actor: the side shown as next on the offer. Next action: counter, accept or let it expire; after expiry make a fresh offer.
  • Accepting creates the agreement and reserves the period in one step

    Allowed:
    On acceptance the agreement and the reservation are saved together or not at all. Terms that match the package start active; different terms wait for reapproval.
    Refused:
    A fully reserved period cannot be accepted. An open offer reserves nothing. Different terms are reapproved only by the restaurant owner or central operations with no tie to the brand. A reservation does not promise printing, installation, footfall or sales.
    Why:
    A period is never sold twice.
    If you need it done:
    Next actor: the restaurant owner or central operations. Next action: reapprove or cancel; for a full period, offer another one.
  • Agreements: terms are fixed; change them by amendment or owner cancellation

    Allowed:
    Any party member proposes one amendment at a time; a member of the other party accepts it; the proposing side can withdraw it. An owner of either party can cancel an active agreement alone, which frees the period.
    Refused:
    Operators and managers cannot cancel. An expired agreement cannot be cancelled. Cancelling is final. Accepted terms are never rewritten. A side cannot accept its own amendment. A member of both parties' organisations is refused on both sides.
    Why:
    Accepted terms are the record; changing them needs the other side.
    If you need it done:
    Next actor: the other party to accept an amendment, the proposing party to withdraw it, or an owner to cancel. Next action: as stated on the agreement.
  • Artwork: the brand uploads, an owner decides the proof, and approval fixes it

    Allowed:
    Brand members upload artwork (PNG, JPEG or PDF, up to 25 MB) while the agreement is active. Any party member generates the proof. The brand owner or restaurant owner approves or rejects it (a rejection needs a reason).
    Refused:
    Restaurant members cannot upload artwork. Operators and managers cannot decide a proof. Only approved artwork is printed and an approved version cannot change. Staff cannot download artwork files.
    Why:
    What is printed must be exactly what an owner approved.
    If you need it done:
    Next actor: the brand (upload) or an owner of either party (decision). Next action: upload a new version or decide the proof.
  • A print request is not an order

    Allowed:
    The brand or restaurant on an active agreement with an approved proof asks for quotes; printers covering that city are invited. An invited printer quotes or declines with a reason; a new quote replaces its earlier one. Any member of either side can choose a quote, which creates the order; the printer then confirms it.
    Refused:
    Nothing becomes an order by itself. Staff cannot quote for a printer. An expired quote, or one above the budget, cannot be chosen. Choosing is final. Printers see the requester's budget. Do not buy stock or print before your order is confirmed.
    Why:
    No volume is promised to any printer, and no requester is bound until they choose.
    If you need it done:
    Next actor: the requester (choose) or the chosen printer (confirm). Next action: choose a valid quote, or confirm the order.
  • The printer records delivery; settlement follows a complete, undamaged delivery

    Allowed:
    The chosen printer records dispatch and delivery, including the count and any damage.
    Refused:
    A damaged delivery asks for a replacement of the whole ordered quantity. Settlement waits for a complete, undamaged delivery and is recorded by central operations; whoever recorded the delivery cannot record its settlement.
    Why:
    Payment follows evidence, recorded by a different person.
    If you need it done:
    Next actor: the printer (replacement) or central operations (settlement). Next action: send the replacement, or record the settlement once paid.
  • Installation jobs: the venue owner controls the job; one installer wins

    Allowed:
    The restaurant owner or central operations creates a job on an active agreement; pay is fixed when created. A venue member offers it to eligible installers; one installer organisation accepts. The installer proposes a time and the restaurant owner confirms it.
    Refused:
    Operators and managers cannot create, confirm, cancel or reopen jobs. A job with no rate cannot be offered. Work cannot start before the venue confirms the time. The restaurant owner can cancel a job that is not completed, with a reason, even after evidence was sent; a cancelled job pays nothing.
    Why:
    The venue hosts the work and decides who comes and when.
    If you need it done:
    Next actor: the restaurant owner (create, confirm, cancel) or the offered installer (accept). Next action: as shown on the job.
  • Evidence: the installer sends it, the restaurant owner acknowledges, someone else decides QA

    Allowed:
    The accepting installer sends 1 to 20 PNG or JPEG photos (up to 10 MB each). The sign-off link is shown once to the installer, who gives it to the restaurant. The restaurant owner (or central operations or the platform owner) acknowledges through it. QA review follows.
    Refused:
    Restaurant operators and managers cannot acknowledge. Keep the sign-off link: it is not shown again. The person who acknowledged cannot also make the QA decision. One dispute at a time per job; only central operations or the platform owner resolve it, and never the person who made the job's QA decision or gave its venue acknowledgement.
    Why:
    Payable work needs two different people to confirm it.
    If you need it done:
    Next actor: the restaurant owner, then an independent QA reviewer. Next action: acknowledge from the link, then QA decides.

Next actor and action: Next actor: restaurant owner for owner-only decisions. Next action: complete in-scope operational fields and route agreements to the authorized owner.

Participant role

Restaurant manager

restaurant_manager

Coordinate work for the restaurant organisation your grant names; access is limited to active organisation membership and the grant's geography. A role received by accepting a Team invitation currently covers every location of that restaurant.

Start and setup

Accept the organisation invitation and confirm location scope before updating operational records.

What to prepare

  • Active grant and assigned location
  • Accurate availability/access information
  • Participant owner for binding terms

Who grants access

The restaurant owner or permitted staff issuer provides membership/grant; the application checks scope on every request.

Limits and gotchas

  • Manager title or venue address does not grant access.
  • A reservation does not guarantee fulfilment; changes may need amendment and reapproval.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Restaurant team: the owner and trusted team members manage people

    Allowed:
    On the Team page an owner invites co-owners, operators and managers by email and removes operators and managers. Operators and managers whose role covers the whole restaurant (everyone who joined by a Team invitation) can also add members and give or remove operator and manager roles; this is intended, so invite only people you trust. A central operations or platform owner role with no place limit can remove people (end a membership, take away an operator or manager role) without a request from the restaurant. Every change is recorded.
    Refused:
    PutYourBrand staff cannot add anyone to a restaurant team or give anyone an operator, manager or owner role, because anyone on a restaurant team can accept offers that bind the restaurant. This includes an owner, operator or manager whose account also holds a staff role. Two separately audited exceptions exist, and in both the owner accepts the invitation themselves: the first owner invitation of an assisted onboarding (only for a restaurant that never had an owner, at the eligible operator's audited start) and an approved two-person owner recovery (only when the restaurant has no active owner). Only an existing owner can make someone an owner, and ending an owner's role or membership needs a central operations or platform owner role with no place limit. Nobody can remove themselves. Removing someone ends every role they held in the restaurant; inviting them again gives only the role in the new invitation. Someone who already has access cannot be invited again: remove and re-invite to change a role. Staff accounts and putyourbrand.in addresses cannot be added. A role from a Team invitation covers every location of the restaurant. An owner whose account also holds a staff role sees no invite form on the Team page; the page names who can invite instead: another owner with no staff role, or an operator or manager covering the whole restaurant (existing accounts, operator or manager roles only), and failing both, central operations ending that owner's staff role. Owner recovery and assisted onboarding do not apply while the restaurant has an owner.
    Why:
    Who acts for a restaurant is the restaurant's decision, run as a trusted team; staff never accept terms for a restaurant, so staff never put someone on its team.
    If you need it done:
    Next actor: an owner of this restaurant, or central operations, through /contact for owner changes. Next action: they make the change.
  • Restaurant setup: steps go in order, and only a restaurant owner accepts

    Allowed:
    Steps 1 to 4 go in order and can be revisited. Step 1 is completed by the person the setup belongs to (who started it or holds its resume link) and makes them owner.
    Refused:
    Skipping steps. Step 5 (accept) is for a restaurant owner with no staff role; operators, managers and staff can review but not accept. If anything changed since you reviewed, reload Review and fees first. Acceptance is final and keeps a fixed record of the terms.
    Why:
    Acceptance binds the restaurant.
    If you need it done:
    Next actor: a restaurant owner. Next action: reload Review and fees if asked, then accept.
  • Venue offers and baseline packages: owner approval, and approved means fixed

    Allowed:
    Any venue member drafts a baseline package or diner offer. The restaurant owner or central operations approves it. A baseline package needs its amount, payer and tax set and an average-bill answer; a diner offer needs a real amount. An owner may approve content they wrote.
    Refused:
    Operators and managers cannot approve. A staff member who prepared it, or a non-owner who wrote it, cannot approve it. Approved or retired packages and offers cannot be edited: create a new one. Pay-per-sale packages are refused.
    Why:
    Brands make offers on the approved package, so it must not change under them.
    If you need it done:
    Next actor: the restaurant owner or central operations. Next action: approve the draft, or create a replacement.
  • Sellable periods: offering one reserves nothing, and sold periods stay

    Allowed:
    Venue members open sellable periods (whole IST days) on active tables and display spots, and retire periods nobody has bid on or bought.
    Refused:
    Side B of a display ("Place your ad here") is never sold. A period with an agreement or an open offer cannot be retired, nor can its table or spot. Retiring is final. A period on sale promises no buyer, footfall or installation.
    Why:
    A brand that bought or is negotiating relies on the period.
    If you need it done:
    Next actor: the venue team. Next action: let an open offer expire or accept it (a counter keeps it open); to free a sold period, an owner of either side cancels the agreement first.
  • Exports are owner-only; the logo can be changed by the wider team

    Allowed:
    Owners export their organisation's data. Anyone whose role covers the whole organisation can change its logo; staff review a new logo before it is public.
    Refused:
    Operators, managers and workers cannot export (for example the tables CSV or QR analytics CSV).
    Why:
    Exporting copies data out of the platform.
    If you need it done:
    Next actor: an owner of your organisation. Next action: they run the export.
  • Pictures: fixed limits and staff review

    Allowed:
    Up to 12 photos per venue location, 3 per display spot, and one logo plus one replacement waiting for review. Approved venue photos and logos are public; display spot photos stay internal.
    Refused:
    Rejected pictures count toward the limit until removed. Editing an approved picture's description takes it off the public page until reviewed again. Nobody reviews their own upload or a picture from their own organisation.
    Why:
    Public pictures must respect rights, consent and accuracy.
    If you need it done:
    Next actor: platform staff covering your city. Next action: they approve the picture or reject it with a reason.
  • Offers: sides take turns, nothing is accepted automatically, and any member of a side can accept

    Allowed:
    A brand member makes a private offer on an approved package. Sides counter in turn. The side that did not propose the latest terms accepts that exact latest version. Any member of that side can accept, including restaurant operators and managers and brand operators.
    Refused:
    Accepting an older version, your own side's terms, or an offer after its expiry (end of the chosen IST day). Countering out of turn. Only the side that proposed the latest terms can withdraw them, and that is final. There is no decline button: counter, or let it expire. An acceptance binds your organisation, so agree internally who accepts.
    Why:
    Each acceptance must answer terms the other side proposed.
    If you need it done:
    Next actor: the side shown as next on the offer. Next action: counter, accept or let it expire; after expiry make a fresh offer.
  • Accepting creates the agreement and reserves the period in one step

    Allowed:
    On acceptance the agreement and the reservation are saved together or not at all. Terms that match the package start active; different terms wait for reapproval.
    Refused:
    A fully reserved period cannot be accepted. An open offer reserves nothing. Different terms are reapproved only by the restaurant owner or central operations with no tie to the brand. A reservation does not promise printing, installation, footfall or sales.
    Why:
    A period is never sold twice.
    If you need it done:
    Next actor: the restaurant owner or central operations. Next action: reapprove or cancel; for a full period, offer another one.
  • Agreements: terms are fixed; change them by amendment or owner cancellation

    Allowed:
    Any party member proposes one amendment at a time; a member of the other party accepts it; the proposing side can withdraw it. An owner of either party can cancel an active agreement alone, which frees the period.
    Refused:
    Operators and managers cannot cancel. An expired agreement cannot be cancelled. Cancelling is final. Accepted terms are never rewritten. A side cannot accept its own amendment. A member of both parties' organisations is refused on both sides.
    Why:
    Accepted terms are the record; changing them needs the other side.
    If you need it done:
    Next actor: the other party to accept an amendment, the proposing party to withdraw it, or an owner to cancel. Next action: as stated on the agreement.
  • Artwork: the brand uploads, an owner decides the proof, and approval fixes it

    Allowed:
    Brand members upload artwork (PNG, JPEG or PDF, up to 25 MB) while the agreement is active. Any party member generates the proof. The brand owner or restaurant owner approves or rejects it (a rejection needs a reason).
    Refused:
    Restaurant members cannot upload artwork. Operators and managers cannot decide a proof. Only approved artwork is printed and an approved version cannot change. Staff cannot download artwork files.
    Why:
    What is printed must be exactly what an owner approved.
    If you need it done:
    Next actor: the brand (upload) or an owner of either party (decision). Next action: upload a new version or decide the proof.
  • A print request is not an order

    Allowed:
    The brand or restaurant on an active agreement with an approved proof asks for quotes; printers covering that city are invited. An invited printer quotes or declines with a reason; a new quote replaces its earlier one. Any member of either side can choose a quote, which creates the order; the printer then confirms it.
    Refused:
    Nothing becomes an order by itself. Staff cannot quote for a printer. An expired quote, or one above the budget, cannot be chosen. Choosing is final. Printers see the requester's budget. Do not buy stock or print before your order is confirmed.
    Why:
    No volume is promised to any printer, and no requester is bound until they choose.
    If you need it done:
    Next actor: the requester (choose) or the chosen printer (confirm). Next action: choose a valid quote, or confirm the order.
  • The printer records delivery; settlement follows a complete, undamaged delivery

    Allowed:
    The chosen printer records dispatch and delivery, including the count and any damage.
    Refused:
    A damaged delivery asks for a replacement of the whole ordered quantity. Settlement waits for a complete, undamaged delivery and is recorded by central operations; whoever recorded the delivery cannot record its settlement.
    Why:
    Payment follows evidence, recorded by a different person.
    If you need it done:
    Next actor: the printer (replacement) or central operations (settlement). Next action: send the replacement, or record the settlement once paid.
  • Installation jobs: the venue owner controls the job; one installer wins

    Allowed:
    The restaurant owner or central operations creates a job on an active agreement; pay is fixed when created. A venue member offers it to eligible installers; one installer organisation accepts. The installer proposes a time and the restaurant owner confirms it.
    Refused:
    Operators and managers cannot create, confirm, cancel or reopen jobs. A job with no rate cannot be offered. Work cannot start before the venue confirms the time. The restaurant owner can cancel a job that is not completed, with a reason, even after evidence was sent; a cancelled job pays nothing.
    Why:
    The venue hosts the work and decides who comes and when.
    If you need it done:
    Next actor: the restaurant owner (create, confirm, cancel) or the offered installer (accept). Next action: as shown on the job.
  • Evidence: the installer sends it, the restaurant owner acknowledges, someone else decides QA

    Allowed:
    The accepting installer sends 1 to 20 PNG or JPEG photos (up to 10 MB each). The sign-off link is shown once to the installer, who gives it to the restaurant. The restaurant owner (or central operations or the platform owner) acknowledges through it. QA review follows.
    Refused:
    Restaurant operators and managers cannot acknowledge. Keep the sign-off link: it is not shown again. The person who acknowledged cannot also make the QA decision. One dispute at a time per job; only central operations or the platform owner resolve it, and never the person who made the job's QA decision or gave its venue acknowledgement.
    Why:
    Payable work needs two different people to confirm it.
    If you need it done:
    Next actor: the restaurant owner, then an independent QA reviewer. Next action: acknowledge from the link, then QA decides.

Next actor and action: Next actor: restaurant owner for approval/signature. Next action: finish assigned location details and escalate any term or access issue.

Participant role

Brand owner

brand_owner

Manage your own brand organisation and available campaign, destination and binding commercial workflows.

Start and setup

Submit a brand enquiry or accept an organisation invitation. Managing members and accepting binding terms do not need an authenticator. An authenticator is optional (set one up at /account/security); only the platform owner must use one.

What to prepare

  • Brand organisation and authorized contact
  • Campaign market, dates and approved destination
  • Approved offer, asset rights and exact agreed terms

Who grants access

An authorized brand owner/staff issuer grants organisation access; the brand owner (or central operations) activates campaigns and approves destination web addresses. No authenticator code is required for binding or membership actions; only the platform owner must use an authenticator.

Limits and gotchas

  • Any brand member creates, edits and submits draft campaigns on /dashboard/brands; only the brand owner (or central operations) activates, resumes or retires them, and activation is refused until the chosen destination web address is approved. An active campaign is not a booking: placements are agreed per venue through offers.
  • Pay-per-sale, checkout and automated settlement are not enabled; reports are not proof of sales or guaranteed reach.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Brand, print partner and installer teams: staff bring in the first owner; the owner adds the team

    Allowed:
    Central operations or the platform owner may invite the first owner of a brand, print partner or installer organisation that has no active owner, and the same path restores an owner when an organisation has lost every owner. Applying as a print partner or installer makes the applicant the owner. Once there is an owner, the owner invites co-owners and operators (installer workers for installers) from the Team page (/dashboard/team). Operators keep their earlier right to invite operators. Owners without staff roles remove non-owner members or end non-owner roles on the Team page. Central operations or a platform owner covering every registered place may remove non-owner access there; only an unrestricted central operations or platform owner grant may end owner access. Each change is audited. Ending membership ends all roles immediately, including for an already signed-in person on the next request.
    Refused:
    Once the organisation has an active owner, PutYourBrand staff cannot add anyone or give anyone a role there, including an owner whose account also holds a staff role (refused as staff_cannot_add_members). An invitation issued by staff, or with no recorded issuer, is refused and stays unused if an owner joined before acceptance; a later end to the issuer's staff role does not unlock it. Only an active owner with no staff role makes someone a co-owner. On the Team page an active owner without a staff role removes a non-owner member or ends a non-owner role. Ending a membership ends all its roles in the same transaction; every change is audited. Central operations or a platform owner may remove members and end non-owner roles where one role covers the whole organisation (an unrestricted role, or one scoped role covering all registered places). Only an unrestricted one may end an owner role or membership. An owner cannot end their own last owner role; staff must end any owner role. A staff-and-owner account acts as staff, not as a non-staff owner.
    Why:
    Brands, print partners and installers agree terms that bind them, so who acts for them is their owner's decision, as for restaurants.
    If you need it done:
    Next actor: an owner of your organisation (invitations and non-owner removal from /dashboard/team), or central operations, through /contact for owner removal or an organisation with no owner. Next action: they make the audited change; a removed person's existing session no longer has those roles on its next request.
  • Exports are owner-only; the logo can be changed by the wider team

    Allowed:
    Owners export their organisation's data. Anyone whose role covers the whole organisation can change its logo; staff review a new logo before it is public.
    Refused:
    Operators, managers and workers cannot export (for example the tables CSV or QR analytics CSV).
    Why:
    Exporting copies data out of the platform.
    If you need it done:
    Next actor: an owner of your organisation. Next action: they run the export.
  • Offers: sides take turns, nothing is accepted automatically, and any member of a side can accept

    Allowed:
    A brand member makes a private offer on an approved package. Sides counter in turn. The side that did not propose the latest terms accepts that exact latest version. Any member of that side can accept, including restaurant operators and managers and brand operators.
    Refused:
    Accepting an older version, your own side's terms, or an offer after its expiry (end of the chosen IST day). Countering out of turn. Only the side that proposed the latest terms can withdraw them, and that is final. There is no decline button: counter, or let it expire. An acceptance binds your organisation, so agree internally who accepts.
    Why:
    Each acceptance must answer terms the other side proposed.
    If you need it done:
    Next actor: the side shown as next on the offer. Next action: counter, accept or let it expire; after expiry make a fresh offer.
  • Accepting creates the agreement and reserves the period in one step

    Allowed:
    On acceptance the agreement and the reservation are saved together or not at all. Terms that match the package start active; different terms wait for reapproval.
    Refused:
    A fully reserved period cannot be accepted. An open offer reserves nothing. Different terms are reapproved only by the restaurant owner or central operations with no tie to the brand. A reservation does not promise printing, installation, footfall or sales.
    Why:
    A period is never sold twice.
    If you need it done:
    Next actor: the restaurant owner or central operations. Next action: reapprove or cancel; for a full period, offer another one.
  • Agreements: terms are fixed; change them by amendment or owner cancellation

    Allowed:
    Any party member proposes one amendment at a time; a member of the other party accepts it; the proposing side can withdraw it. An owner of either party can cancel an active agreement alone, which frees the period.
    Refused:
    Operators and managers cannot cancel. An expired agreement cannot be cancelled. Cancelling is final. Accepted terms are never rewritten. A side cannot accept its own amendment. A member of both parties' organisations is refused on both sides.
    Why:
    Accepted terms are the record; changing them needs the other side.
    If you need it done:
    Next actor: the other party to accept an amendment, the proposing party to withdraw it, or an owner to cancel. Next action: as stated on the agreement.
  • Artwork: the brand uploads, an owner decides the proof, and approval fixes it

    Allowed:
    Brand members upload artwork (PNG, JPEG or PDF, up to 25 MB) while the agreement is active. Any party member generates the proof. The brand owner or restaurant owner approves or rejects it (a rejection needs a reason).
    Refused:
    Restaurant members cannot upload artwork. Operators and managers cannot decide a proof. Only approved artwork is printed and an approved version cannot change. Staff cannot download artwork files.
    Why:
    What is printed must be exactly what an owner approved.
    If you need it done:
    Next actor: the brand (upload) or an owner of either party (decision). Next action: upload a new version or decide the proof.
  • A placement goes live only when all seven steps are done

    Allowed:
    The restaurant owner, brand owner or a platform operator activates once there are approved terms, an approved proof, a confirmed print order, a completed installation, the venue sign-off, independent QA and a recorded settlement of the installer's earning.
    Refused:
    Operators and managers cannot activate. A staff waiver blocks a step rather than completing it. Activation is final; pausing is the only reverse, and resuming re-checks every step.
    Why:
    Going live is where every earlier step must be shown.
    If you need it done:
    Next actor: whoever owns the first missing step, named on the activation panel. Next action: complete it, then retry.
  • Campaigns: any member drafts; the brand owner activates and approves web addresses

    Allowed:
    Any brand member creates, edits and submits draft campaigns, requests destination web addresses and pauses an active campaign.
    Refused:
    Only the brand owner or central operations activates, resumes or retires a campaign or approves a web address. Activation waits for an approved address. An address decision is final. Only drafts can be edited; retired is final. An active campaign books nothing at a venue. Only an active brand owner with no staff role makes someone a co-owner (central operations only while the brand has no owner); only central operations ends the brand owner role.
    Why:
    Where diners are sent is the brand owner's responsibility.
    If you need it done:
    Next actor: the brand owner. Next action: approve the address and activate; for changed terms, create a new campaign.
  • A print request is not an order

    Allowed:
    The brand or restaurant on an active agreement with an approved proof asks for quotes; printers covering that city are invited. An invited printer quotes or declines with a reason; a new quote replaces its earlier one. Any member of either side can choose a quote, which creates the order; the printer then confirms it.
    Refused:
    Nothing becomes an order by itself. Staff cannot quote for a printer. An expired quote, or one above the budget, cannot be chosen. Choosing is final. Printers see the requester's budget. Do not buy stock or print before your order is confirmed.
    Why:
    No volume is promised to any printer, and no requester is bound until they choose.
    If you need it done:
    Next actor: the requester (choose) or the chosen printer (confirm). Next action: choose a valid quote, or confirm the order.
  • The printer records delivery; settlement follows a complete, undamaged delivery

    Allowed:
    The chosen printer records dispatch and delivery, including the count and any damage.
    Refused:
    A damaged delivery asks for a replacement of the whole ordered quantity. Settlement waits for a complete, undamaged delivery and is recorded by central operations; whoever recorded the delivery cannot record its settlement.
    Why:
    Payment follows evidence, recorded by a different person.
    If you need it done:
    Next actor: the printer (replacement) or central operations (settlement). Next action: send the replacement, or record the settlement once paid.

Next actor and action: Next actor: the brand owner. Next action: approve the destination web address and activate submitted campaigns on /dashboard/brands; venues in the campaign market can then select it in onboarding.

Participant role

Brand operator

brand_operator

Work with the campaign and offer records currently available to your brand organisation; owner-only approvals remain with an authorized owner.

Start and setup

Accept an invitation to the correct brand organisation and confirm the scope before uploading assets or preparing campaigns.

What to prepare

  • Active brand membership
  • Approved destination and authorized asset
  • Owner contact for binding acceptance

Who grants access

A brand owner or authorized issuer manages membership; participant organisation and server scope checks apply to every request.

Limits and gotchas

  • You can create, edit and submit draft campaigns and request destination web addresses on /dashboard/brands, and pause an active campaign; activating, resuming and retiring campaigns and approving destinations are the brand owner's (or central operations').
  • Do not claim approval from a submitted draft. No diner personal data or unrelated restaurant contact export is provided by default.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Brand, print partner and installer teams: staff bring in the first owner; the owner adds the team

    Allowed:
    Central operations or the platform owner may invite the first owner of a brand, print partner or installer organisation that has no active owner, and the same path restores an owner when an organisation has lost every owner. Applying as a print partner or installer makes the applicant the owner. Once there is an owner, the owner invites co-owners and operators (installer workers for installers) from the Team page (/dashboard/team). Operators keep their earlier right to invite operators. Owners without staff roles remove non-owner members or end non-owner roles on the Team page. Central operations or a platform owner covering every registered place may remove non-owner access there; only an unrestricted central operations or platform owner grant may end owner access. Each change is audited. Ending membership ends all roles immediately, including for an already signed-in person on the next request.
    Refused:
    Once the organisation has an active owner, PutYourBrand staff cannot add anyone or give anyone a role there, including an owner whose account also holds a staff role (refused as staff_cannot_add_members). An invitation issued by staff, or with no recorded issuer, is refused and stays unused if an owner joined before acceptance; a later end to the issuer's staff role does not unlock it. Only an active owner with no staff role makes someone a co-owner. On the Team page an active owner without a staff role removes a non-owner member or ends a non-owner role. Ending a membership ends all its roles in the same transaction; every change is audited. Central operations or a platform owner may remove members and end non-owner roles where one role covers the whole organisation (an unrestricted role, or one scoped role covering all registered places). Only an unrestricted one may end an owner role or membership. An owner cannot end their own last owner role; staff must end any owner role. A staff-and-owner account acts as staff, not as a non-staff owner.
    Why:
    Brands, print partners and installers agree terms that bind them, so who acts for them is their owner's decision, as for restaurants.
    If you need it done:
    Next actor: an owner of your organisation (invitations and non-owner removal from /dashboard/team), or central operations, through /contact for owner removal or an organisation with no owner. Next action: they make the audited change; a removed person's existing session no longer has those roles on its next request.
  • Exports are owner-only; the logo can be changed by the wider team

    Allowed:
    Owners export their organisation's data. Anyone whose role covers the whole organisation can change its logo; staff review a new logo before it is public.
    Refused:
    Operators, managers and workers cannot export (for example the tables CSV or QR analytics CSV).
    Why:
    Exporting copies data out of the platform.
    If you need it done:
    Next actor: an owner of your organisation. Next action: they run the export.
  • Offers: sides take turns, nothing is accepted automatically, and any member of a side can accept

    Allowed:
    A brand member makes a private offer on an approved package. Sides counter in turn. The side that did not propose the latest terms accepts that exact latest version. Any member of that side can accept, including restaurant operators and managers and brand operators.
    Refused:
    Accepting an older version, your own side's terms, or an offer after its expiry (end of the chosen IST day). Countering out of turn. Only the side that proposed the latest terms can withdraw them, and that is final. There is no decline button: counter, or let it expire. An acceptance binds your organisation, so agree internally who accepts.
    Why:
    Each acceptance must answer terms the other side proposed.
    If you need it done:
    Next actor: the side shown as next on the offer. Next action: counter, accept or let it expire; after expiry make a fresh offer.
  • Accepting creates the agreement and reserves the period in one step

    Allowed:
    On acceptance the agreement and the reservation are saved together or not at all. Terms that match the package start active; different terms wait for reapproval.
    Refused:
    A fully reserved period cannot be accepted. An open offer reserves nothing. Different terms are reapproved only by the restaurant owner or central operations with no tie to the brand. A reservation does not promise printing, installation, footfall or sales.
    Why:
    A period is never sold twice.
    If you need it done:
    Next actor: the restaurant owner or central operations. Next action: reapprove or cancel; for a full period, offer another one.
  • Agreements: terms are fixed; change them by amendment or owner cancellation

    Allowed:
    Any party member proposes one amendment at a time; a member of the other party accepts it; the proposing side can withdraw it. An owner of either party can cancel an active agreement alone, which frees the period.
    Refused:
    Operators and managers cannot cancel. An expired agreement cannot be cancelled. Cancelling is final. Accepted terms are never rewritten. A side cannot accept its own amendment. A member of both parties' organisations is refused on both sides.
    Why:
    Accepted terms are the record; changing them needs the other side.
    If you need it done:
    Next actor: the other party to accept an amendment, the proposing party to withdraw it, or an owner to cancel. Next action: as stated on the agreement.
  • Artwork: the brand uploads, an owner decides the proof, and approval fixes it

    Allowed:
    Brand members upload artwork (PNG, JPEG or PDF, up to 25 MB) while the agreement is active. Any party member generates the proof. The brand owner or restaurant owner approves or rejects it (a rejection needs a reason).
    Refused:
    Restaurant members cannot upload artwork. Operators and managers cannot decide a proof. Only approved artwork is printed and an approved version cannot change. Staff cannot download artwork files.
    Why:
    What is printed must be exactly what an owner approved.
    If you need it done:
    Next actor: the brand (upload) or an owner of either party (decision). Next action: upload a new version or decide the proof.
  • Campaigns: any member drafts; the brand owner activates and approves web addresses

    Allowed:
    Any brand member creates, edits and submits draft campaigns, requests destination web addresses and pauses an active campaign.
    Refused:
    Only the brand owner or central operations activates, resumes or retires a campaign or approves a web address. Activation waits for an approved address. An address decision is final. Only drafts can be edited; retired is final. An active campaign books nothing at a venue. Only an active brand owner with no staff role makes someone a co-owner (central operations only while the brand has no owner); only central operations ends the brand owner role.
    Why:
    Where diners are sent is the brand owner's responsibility.
    If you need it done:
    Next actor: the brand owner. Next action: approve the address and activate; for changed terms, create a new campaign.
  • A print request is not an order

    Allowed:
    The brand or restaurant on an active agreement with an approved proof asks for quotes; printers covering that city are invited. An invited printer quotes or declines with a reason; a new quote replaces its earlier one. Any member of either side can choose a quote, which creates the order; the printer then confirms it.
    Refused:
    Nothing becomes an order by itself. Staff cannot quote for a printer. An expired quote, or one above the budget, cannot be chosen. Choosing is final. Printers see the requester's budget. Do not buy stock or print before your order is confirmed.
    Why:
    No volume is promised to any printer, and no requester is bound until they choose.
    If you need it done:
    Next actor: the requester (choose) or the chosen printer (confirm). Next action: choose a valid quote, or confirm the order.
  • The printer records delivery; settlement follows a complete, undamaged delivery

    Allowed:
    The chosen printer records dispatch and delivery, including the count and any damage.
    Refused:
    A damaged delivery asks for a replacement of the whole ordered quantity. Settlement waits for a complete, undamaged delivery and is recorded by central operations; whoever recorded the delivery cannot record its settlement.
    Why:
    Payment follows evidence, recorded by a different person.
    If you need it done:
    Next actor: the printer (replacement) or central operations (settlement). Next action: send the replacement, or record the settlement once paid.

Next actor and action: Next actor: you for drafts and submission, then the brand owner. Next action: submit the draft campaign on /dashboard/brands; the brand owner approves its destination and activates it.

Participant role

Printer owner

printer_owner

Manage your own print-provider organisation, service profile, membership and owner-authorized work decisions.

Start and setup

Respond to an enquiry and accept an approved printer-organisation invitation; use the dedicated portal after access is granted.

What to prepare

  • Capabilities and service coverage
  • Quote scope, quantity, timing and price requested
  • Proof and delivery evidence when a real approved order exists

Who grants access

An authorized issuer/organisation owner grants access; owner membership changes do not need an authenticator code (only the platform owner must use one). Quotes are reviewed; they do not become orders automatically.

Limits and gotchas

  • No guaranteed volume or automatic order/payment.
  • Do not submit sensitive financial credentials through enquiry forms.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Brand, print partner and installer teams: staff bring in the first owner; the owner adds the team

    Allowed:
    Central operations or the platform owner may invite the first owner of a brand, print partner or installer organisation that has no active owner, and the same path restores an owner when an organisation has lost every owner. Applying as a print partner or installer makes the applicant the owner. Once there is an owner, the owner invites co-owners and operators (installer workers for installers) from the Team page (/dashboard/team). Operators keep their earlier right to invite operators. Owners without staff roles remove non-owner members or end non-owner roles on the Team page. Central operations or a platform owner covering every registered place may remove non-owner access there; only an unrestricted central operations or platform owner grant may end owner access. Each change is audited. Ending membership ends all roles immediately, including for an already signed-in person on the next request.
    Refused:
    Once the organisation has an active owner, PutYourBrand staff cannot add anyone or give anyone a role there, including an owner whose account also holds a staff role (refused as staff_cannot_add_members). An invitation issued by staff, or with no recorded issuer, is refused and stays unused if an owner joined before acceptance; a later end to the issuer's staff role does not unlock it. Only an active owner with no staff role makes someone a co-owner. On the Team page an active owner without a staff role removes a non-owner member or ends a non-owner role. Ending a membership ends all its roles in the same transaction; every change is audited. Central operations or a platform owner may remove members and end non-owner roles where one role covers the whole organisation (an unrestricted role, or one scoped role covering all registered places). Only an unrestricted one may end an owner role or membership. An owner cannot end their own last owner role; staff must end any owner role. A staff-and-owner account acts as staff, not as a non-staff owner.
    Why:
    Brands, print partners and installers agree terms that bind them, so who acts for them is their owner's decision, as for restaurants.
    If you need it done:
    Next actor: an owner of your organisation (invitations and non-owner removal from /dashboard/team), or central operations, through /contact for owner removal or an organisation with no owner. Next action: they make the audited change; a removed person's existing session no longer has those roles on its next request.
  • Exports are owner-only; the logo can be changed by the wider team

    Allowed:
    Owners export their organisation's data. Anyone whose role covers the whole organisation can change its logo; staff review a new logo before it is public.
    Refused:
    Operators, managers and workers cannot export (for example the tables CSV or QR analytics CSV).
    Why:
    Exporting copies data out of the platform.
    If you need it done:
    Next actor: an owner of your organisation. Next action: they run the export.
  • Printers: applying is not approval; matching uses your current profile

    Allowed:
    A signed-in account registers a printer organisation; it starts pending until central operations or the platform owner approve it. Approved printers are matched on their current service cities and capabilities; later edits apply straight away without a new review. Matching can also suggest printers in nearby cities.
    Refused:
    Your home city counts only if it is in your service cities. A staff member who belongs to your organisation cannot approve it. Only an active printer owner with no staff role makes someone a co-owner (central operations only while the printer has no owner); only central operations ends the printer owner role. You cannot remove your own membership. A printer or brand role never allows running a match.
    Why:
    Keep your profile accurate: requests are matched on what it says.
    If you need it done:
    Next actor: central operations. Next action: review your printer organisation, or answer questions about your profile.
  • A print request is not an order

    Allowed:
    The brand or restaurant on an active agreement with an approved proof asks for quotes; printers covering that city are invited. An invited printer quotes or declines with a reason; a new quote replaces its earlier one. Any member of either side can choose a quote, which creates the order; the printer then confirms it.
    Refused:
    Nothing becomes an order by itself. Staff cannot quote for a printer. An expired quote, or one above the budget, cannot be chosen. Choosing is final. Printers see the requester's budget. Do not buy stock or print before your order is confirmed.
    Why:
    No volume is promised to any printer, and no requester is bound until they choose.
    If you need it done:
    Next actor: the requester (choose) or the chosen printer (confirm). Next action: choose a valid quote, or confirm the order.
  • The printer records delivery; settlement follows a complete, undamaged delivery

    Allowed:
    The chosen printer records dispatch and delivery, including the count and any damage.
    Refused:
    A damaged delivery asks for a replacement of the whole ordered quantity. Settlement waits for a complete, undamaged delivery and is recorded by central operations; whoever recorded the delivery cannot record its settlement.
    Why:
    Payment follows evidence, recorded by a different person.
    If you need it done:
    Next actor: the printer (replacement) or central operations (settlement). Next action: send the replacement, or record the settlement once paid.

Next actor and action: Next actor: printer owner for the quote, then requester for selection and authorized operations for order release. Next action: quote only the stated RFQ and wait for selection.

Participant role

Printer operator

printer_operator

Respond to work assigned to your printer organisation; other suppliers and customer records remain out of scope.

Start and setup

Accept an invitation to the correct printer organisation and open the dedicated portal.

What to prepare

  • Organisation membership and service capabilities
  • RFQ details and requested quote fields
  • Proof/delivery evidence required by the order

Who grants access

The printer owner or authorized issuer controls membership; every portal action rechecks the organisation.

Limits and gotchas

  • RFQ is not an order. Do not purchase stock or dispatch until an approved order exists.
  • Only approved proof and scope should be fulfilled.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Brand, print partner and installer teams: staff bring in the first owner; the owner adds the team

    Allowed:
    Central operations or the platform owner may invite the first owner of a brand, print partner or installer organisation that has no active owner, and the same path restores an owner when an organisation has lost every owner. Applying as a print partner or installer makes the applicant the owner. Once there is an owner, the owner invites co-owners and operators (installer workers for installers) from the Team page (/dashboard/team). Operators keep their earlier right to invite operators. Owners without staff roles remove non-owner members or end non-owner roles on the Team page. Central operations or a platform owner covering every registered place may remove non-owner access there; only an unrestricted central operations or platform owner grant may end owner access. Each change is audited. Ending membership ends all roles immediately, including for an already signed-in person on the next request.
    Refused:
    Once the organisation has an active owner, PutYourBrand staff cannot add anyone or give anyone a role there, including an owner whose account also holds a staff role (refused as staff_cannot_add_members). An invitation issued by staff, or with no recorded issuer, is refused and stays unused if an owner joined before acceptance; a later end to the issuer's staff role does not unlock it. Only an active owner with no staff role makes someone a co-owner. On the Team page an active owner without a staff role removes a non-owner member or ends a non-owner role. Ending a membership ends all its roles in the same transaction; every change is audited. Central operations or a platform owner may remove members and end non-owner roles where one role covers the whole organisation (an unrestricted role, or one scoped role covering all registered places). Only an unrestricted one may end an owner role or membership. An owner cannot end their own last owner role; staff must end any owner role. A staff-and-owner account acts as staff, not as a non-staff owner.
    Why:
    Brands, print partners and installers agree terms that bind them, so who acts for them is their owner's decision, as for restaurants.
    If you need it done:
    Next actor: an owner of your organisation (invitations and non-owner removal from /dashboard/team), or central operations, through /contact for owner removal or an organisation with no owner. Next action: they make the audited change; a removed person's existing session no longer has those roles on its next request.
  • Exports are owner-only; the logo can be changed by the wider team

    Allowed:
    Owners export their organisation's data. Anyone whose role covers the whole organisation can change its logo; staff review a new logo before it is public.
    Refused:
    Operators, managers and workers cannot export (for example the tables CSV or QR analytics CSV).
    Why:
    Exporting copies data out of the platform.
    If you need it done:
    Next actor: an owner of your organisation. Next action: they run the export.
  • Printers: applying is not approval; matching uses your current profile

    Allowed:
    A signed-in account registers a printer organisation; it starts pending until central operations or the platform owner approve it. Approved printers are matched on their current service cities and capabilities; later edits apply straight away without a new review. Matching can also suggest printers in nearby cities.
    Refused:
    Your home city counts only if it is in your service cities. A staff member who belongs to your organisation cannot approve it. Only an active printer owner with no staff role makes someone a co-owner (central operations only while the printer has no owner); only central operations ends the printer owner role. You cannot remove your own membership. A printer or brand role never allows running a match.
    Why:
    Keep your profile accurate: requests are matched on what it says.
    If you need it done:
    Next actor: central operations. Next action: review your printer organisation, or answer questions about your profile.
  • A print request is not an order

    Allowed:
    The brand or restaurant on an active agreement with an approved proof asks for quotes; printers covering that city are invited. An invited printer quotes or declines with a reason; a new quote replaces its earlier one. Any member of either side can choose a quote, which creates the order; the printer then confirms it.
    Refused:
    Nothing becomes an order by itself. Staff cannot quote for a printer. An expired quote, or one above the budget, cannot be chosen. Choosing is final. Printers see the requester's budget. Do not buy stock or print before your order is confirmed.
    Why:
    No volume is promised to any printer, and no requester is bound until they choose.
    If you need it done:
    Next actor: the requester (choose) or the chosen printer (confirm). Next action: choose a valid quote, or confirm the order.
  • The printer records delivery; settlement follows a complete, undamaged delivery

    Allowed:
    The chosen printer records dispatch and delivery, including the count and any damage.
    Refused:
    A damaged delivery asks for a replacement of the whole ordered quantity. Settlement waits for a complete, undamaged delivery and is recorded by central operations; whoever recorded the delivery cannot record its settlement.
    Why:
    Payment follows evidence, recorded by a different person.
    If you need it done:
    Next actor: the printer (replacement) or central operations (settlement). Next action: send the replacement, or record the settlement once paid.

Next actor and action: Next actor: printer operator for a requested quote/proof/delivery step; requester for quote selection. Next action: complete the assigned action and wait for explicit approval where required.

Participant role

Installer owner

installer_owner

Manage your installer organisation and authorized members; installer job-offer acceptance currently has no fresh-MFA check in its route.

Start and setup

Apply through the installer path, then accept an organisation invitation after eligibility review.

What to prepare

  • Eligibility and service coverage requested by application
  • Accepted job scope and rate snapshot
  • Evidence and venue acknowledgement for completed work

Who grants access

An authorized issuer grants organisation access; qualification and job access are separate reviewed states. No authenticator code is required: only the platform owner must use an authenticator, and the installer job-offer acceptance route does not check one.

Limits and gotchas

  • No guaranteed jobs or earnings.
  • Scans do not create earnings; work must be accepted, acknowledged by the venue and independently reviewed. Settlement is manual.
  • Accepting a job offer does not ask for an authenticator code; an authenticator is optional at /account/security.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Brand, print partner and installer teams: staff bring in the first owner; the owner adds the team

    Allowed:
    Central operations or the platform owner may invite the first owner of a brand, print partner or installer organisation that has no active owner, and the same path restores an owner when an organisation has lost every owner. Applying as a print partner or installer makes the applicant the owner. Once there is an owner, the owner invites co-owners and operators (installer workers for installers) from the Team page (/dashboard/team). Operators keep their earlier right to invite operators. Owners without staff roles remove non-owner members or end non-owner roles on the Team page. Central operations or a platform owner covering every registered place may remove non-owner access there; only an unrestricted central operations or platform owner grant may end owner access. Each change is audited. Ending membership ends all roles immediately, including for an already signed-in person on the next request.
    Refused:
    Once the organisation has an active owner, PutYourBrand staff cannot add anyone or give anyone a role there, including an owner whose account also holds a staff role (refused as staff_cannot_add_members). An invitation issued by staff, or with no recorded issuer, is refused and stays unused if an owner joined before acceptance; a later end to the issuer's staff role does not unlock it. Only an active owner with no staff role makes someone a co-owner. On the Team page an active owner without a staff role removes a non-owner member or ends a non-owner role. Ending a membership ends all its roles in the same transaction; every change is audited. Central operations or a platform owner may remove members and end non-owner roles where one role covers the whole organisation (an unrestricted role, or one scoped role covering all registered places). Only an unrestricted one may end an owner role or membership. An owner cannot end their own last owner role; staff must end any owner role. A staff-and-owner account acts as staff, not as a non-staff owner.
    Why:
    Brands, print partners and installers agree terms that bind them, so who acts for them is their owner's decision, as for restaurants.
    If you need it done:
    Next actor: an owner of your organisation (invitations and non-owner removal from /dashboard/team), or central operations, through /contact for owner removal or an organisation with no owner. Next action: they make the audited change; a removed person's existing session no longer has those roles on its next request.
  • Exports are owner-only; the logo can be changed by the wider team

    Allowed:
    Owners export their organisation's data. Anyone whose role covers the whole organisation can change its logo; staff review a new logo before it is public.
    Refused:
    Operators, managers and workers cannot export (for example the tables CSV or QR analytics CSV).
    Why:
    Exporting copies data out of the platform.
    If you need it done:
    Next actor: an owner of your organisation. Next action: they run the export.
  • Installers: applying is not approval or a job offer

    Allowed:
    An application creates your installer record. Central operations or the platform owner review it; qualification is given only from under review. Offers go only to installers who are qualified, have a skill, serve the job's city and have a current training record.
    Refused:
    A staff member who belongs to your organisation cannot qualify it. A qualified installer can be moved to not qualified or inactive; inactive goes back through review. No job, number of jobs or earnings is promised.
    Why:
    Work goes only to reviewed, eligible installers.
    If you need it done:
    Next actor: central operations. Next action: review your application; follow the progress page's current request.
  • Installation jobs: the venue owner controls the job; one installer wins

    Allowed:
    The restaurant owner or central operations creates a job on an active agreement; pay is fixed when created. A venue member offers it to eligible installers; one installer organisation accepts. The installer proposes a time and the restaurant owner confirms it.
    Refused:
    Operators and managers cannot create, confirm, cancel or reopen jobs. A job with no rate cannot be offered. Work cannot start before the venue confirms the time. The restaurant owner can cancel a job that is not completed, with a reason, even after evidence was sent; a cancelled job pays nothing.
    Why:
    The venue hosts the work and decides who comes and when.
    If you need it done:
    Next actor: the restaurant owner (create, confirm, cancel) or the offered installer (accept). Next action: as shown on the job.
  • Evidence: the installer sends it, the restaurant owner acknowledges, someone else decides QA

    Allowed:
    The accepting installer sends 1 to 20 PNG or JPEG photos (up to 10 MB each). The sign-off link is shown once to the installer, who gives it to the restaurant. The restaurant owner (or central operations or the platform owner) acknowledges through it. QA review follows.
    Refused:
    Restaurant operators and managers cannot acknowledge. Keep the sign-off link: it is not shown again. The person who acknowledged cannot also make the QA decision. One dispute at a time per job; only central operations or the platform owner resolve it, and never the person who made the job's QA decision or gave its venue acknowledgement.
    Why:
    Payable work needs two different people to confirm it.
    If you need it done:
    Next actor: the restaurant owner, then an independent QA reviewer. Next action: acknowledge from the link, then QA decides.
  • Installer earnings: accepted work only, never scans, settled by hand

    Allowed:
    You are paid for the smaller of the venue-accepted and QA-accepted counts on the same evidence. Earnings appear after central operations recomputes them, and are settled by a record after payment outside the platform.
    Refused:
    QR scans never create earnings. Self-reported work alone is never paid. An earning on hold or disputed, or whose job has an open dispute, cannot be settled until that is resolved. A cancelled job's unsettled earnings are withdrawn at the next recompute. The person who sent the evidence, the QA reviewer and anyone in the installer organisation cannot record the settlement. No amount or date is promised.
    Why:
    Pay follows independently accepted work.
    If you need it done:
    Next actor: central operations. Next action: resolve any hold or dispute, recompute earnings and record the settlement once paid.

Next actor and action: Next actor: installer applicant for requested qualifications, then reviewer for approval. Next action: follow the visible application/job step; do not self-approve earnings.

Participant role

Installer worker

installer_worker

See eligible job summaries and assigned work within the installer organisation; other workers' records and restaurant CRM are not visible.

Start and setup

Complete the installer application and qualification steps, then accept an organisation invitation and assigned job only when eligible.

What to prepare

  • Application and qualification details
  • Exact job scope, schedule and approved earnings basis
  • Evidence, venue acknowledgement and QA requirements

Who grants access

The installer owner/authorized issuer manages organisation membership; platform/authorized reviewers control eligibility and independent QA.

Limits and gotchas

  • No earnings guarantee or payout from scans.
  • Do not begin work until the offer/job and terms are accepted; unresolved issues go through the dispute path.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Brand, print partner and installer teams: staff bring in the first owner; the owner adds the team

    Allowed:
    Central operations or the platform owner may invite the first owner of a brand, print partner or installer organisation that has no active owner, and the same path restores an owner when an organisation has lost every owner. Applying as a print partner or installer makes the applicant the owner. Once there is an owner, the owner invites co-owners and operators (installer workers for installers) from the Team page (/dashboard/team). Operators keep their earlier right to invite operators. Owners without staff roles remove non-owner members or end non-owner roles on the Team page. Central operations or a platform owner covering every registered place may remove non-owner access there; only an unrestricted central operations or platform owner grant may end owner access. Each change is audited. Ending membership ends all roles immediately, including for an already signed-in person on the next request.
    Refused:
    Once the organisation has an active owner, PutYourBrand staff cannot add anyone or give anyone a role there, including an owner whose account also holds a staff role (refused as staff_cannot_add_members). An invitation issued by staff, or with no recorded issuer, is refused and stays unused if an owner joined before acceptance; a later end to the issuer's staff role does not unlock it. Only an active owner with no staff role makes someone a co-owner. On the Team page an active owner without a staff role removes a non-owner member or ends a non-owner role. Ending a membership ends all its roles in the same transaction; every change is audited. Central operations or a platform owner may remove members and end non-owner roles where one role covers the whole organisation (an unrestricted role, or one scoped role covering all registered places). Only an unrestricted one may end an owner role or membership. An owner cannot end their own last owner role; staff must end any owner role. A staff-and-owner account acts as staff, not as a non-staff owner.
    Why:
    Brands, print partners and installers agree terms that bind them, so who acts for them is their owner's decision, as for restaurants.
    If you need it done:
    Next actor: an owner of your organisation (invitations and non-owner removal from /dashboard/team), or central operations, through /contact for owner removal or an organisation with no owner. Next action: they make the audited change; a removed person's existing session no longer has those roles on its next request.
  • Exports are owner-only; the logo can be changed by the wider team

    Allowed:
    Owners export their organisation's data. Anyone whose role covers the whole organisation can change its logo; staff review a new logo before it is public.
    Refused:
    Operators, managers and workers cannot export (for example the tables CSV or QR analytics CSV).
    Why:
    Exporting copies data out of the platform.
    If you need it done:
    Next actor: an owner of your organisation. Next action: they run the export.
  • Installers: applying is not approval or a job offer

    Allowed:
    An application creates your installer record. Central operations or the platform owner review it; qualification is given only from under review. Offers go only to installers who are qualified, have a skill, serve the job's city and have a current training record.
    Refused:
    A staff member who belongs to your organisation cannot qualify it. A qualified installer can be moved to not qualified or inactive; inactive goes back through review. No job, number of jobs or earnings is promised.
    Why:
    Work goes only to reviewed, eligible installers.
    If you need it done:
    Next actor: central operations. Next action: review your application; follow the progress page's current request.
  • Installation jobs: the venue owner controls the job; one installer wins

    Allowed:
    The restaurant owner or central operations creates a job on an active agreement; pay is fixed when created. A venue member offers it to eligible installers; one installer organisation accepts. The installer proposes a time and the restaurant owner confirms it.
    Refused:
    Operators and managers cannot create, confirm, cancel or reopen jobs. A job with no rate cannot be offered. Work cannot start before the venue confirms the time. The restaurant owner can cancel a job that is not completed, with a reason, even after evidence was sent; a cancelled job pays nothing.
    Why:
    The venue hosts the work and decides who comes and when.
    If you need it done:
    Next actor: the restaurant owner (create, confirm, cancel) or the offered installer (accept). Next action: as shown on the job.
  • Evidence: the installer sends it, the restaurant owner acknowledges, someone else decides QA

    Allowed:
    The accepting installer sends 1 to 20 PNG or JPEG photos (up to 10 MB each). The sign-off link is shown once to the installer, who gives it to the restaurant. The restaurant owner (or central operations or the platform owner) acknowledges through it. QA review follows.
    Refused:
    Restaurant operators and managers cannot acknowledge. Keep the sign-off link: it is not shown again. The person who acknowledged cannot also make the QA decision. One dispute at a time per job; only central operations or the platform owner resolve it, and never the person who made the job's QA decision or gave its venue acknowledgement.
    Why:
    Payable work needs two different people to confirm it.
    If you need it done:
    Next actor: the restaurant owner, then an independent QA reviewer. Next action: acknowledge from the link, then QA decides.
  • Installer earnings: accepted work only, never scans, settled by hand

    Allowed:
    You are paid for the smaller of the venue-accepted and QA-accepted counts on the same evidence. Earnings appear after central operations recomputes them, and are settled by a record after payment outside the platform.
    Refused:
    QR scans never create earnings. Self-reported work alone is never paid. An earning on hold or disputed, or whose job has an open dispute, cannot be settled until that is resolved. A cancelled job's unsettled earnings are withdrawn at the next recompute. The person who sent the evidence, the QA reviewer and anyone in the installer organisation cannot record the settlement. No amount or date is promised.
    Why:
    Pay follows independently accepted work.
    If you need it done:
    Next actor: central operations. Next action: resolve any hold or dispute, recompute earnings and record the settlement once paid.

Next actor and action: Next actor: assigned installer for accepted work, then venue for acknowledgement and an independent reviewer for QA. Next action: complete the job evidence or raise the named issue.

Internal role

Finance reviewer

finance_reviewer

Review scoped obligations, disputes and settlement records; cannot make self-reported installation work payable.

Start and setup

Accept an internal invitation and sign in with your password before accessing finance records.

What to prepare

  • Internal grant and allowed scope
  • Accepted terms and supporting evidence
  • Independent approval and duplicate/over-settlement checks

Who grants access

An authorized internal issuer grants this role; server-side scope and action policies decide every record. Self-approval is prohibited.

Limits and gotchas

  • The /admin surface does not admit finance_reviewer. Earnings pages require an installer-organisation grant or global operator access; finance-only access does not expose installer earnings. Statements remain the primary finance destination.
  • Settlement is manual; no online checkout or automated transfer. Never rewrite/delete immutable terms or treat scans as payable proof.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • A PutYourBrand staff account never joins, owns or accepts terms for a restaurant

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators may start an audited assisted onboarding and prepare steps the owner reviews. Finance and QA reviewers cannot.
    Refused:
    An account with any staff role, or a putyourbrand.in email address, cannot be added to a restaurant or accept its agreement, even if it also holds that restaurant's owner role.
    Why:
    Acceptance must come from the restaurant itself.
    If you need it done:
    Next actor: the restaurant owner, on an account with no staff role. Next action: they accept, or add their own non-staff person. Former staff ask central operations to end their staff roles first.
  • Staff roles: who may give which role, where

    Allowed:
    The platform owner, central operations and country, city and area managers give staff roles. Ranks: platform owner 100; central operations, QA reviewer, finance reviewer 90; country manager 60; city manager 40; area manager and sales/BNI coordinator 20. You may give a role of your rank or lower, for a place equal to or inside your own.
    Refused:
    A higher-ranked role; a wider place; a role with no place limit (unless you are platform owner or central operations with no limit); a role for yourself; a role for someone who is not a member of the platform organisation; an expiry that is not in the future. One of your roles must cover all of this by itself.
    Why:
    It stops a manager from choosing who reviews their own work, and stops authority growing beyond what was given.
    If you need it done:
    Next actor: an issuer of equal or higher rank who covers the place (a platform owner for platform owner roles). Next action: they give the role; the person must have accepted a platform invitation first.
  • Staff roles: ending a role takes effect at once, within your rank and place

    Allowed:
    An issuer may end a staff role of equal or lower rank inside their own place. It stops on the holder's next action and is audited with who ended which role and when.
    Refused:
    Ending your own role; ending a higher-ranked role (central operations cannot end a platform owner role); ending a role with no place limit, or outside your place, unless you are platform owner or central operations with no limit.
    Why:
    Roles must be removable quickly, but only by someone who could have given them.
    If you need it done:
    Next actor: central operations (a platform owner for platform owner roles). Next action: they end the role on the Team page.
  • Admin is for the platform owner, central operations and country, city and area managers

    Allowed:
    Those roles open /admin. A manager limited to a place sees and acts on records in that place only.
    Refused:
    Sales/BNI coordinators, finance and QA reviewers and all restaurant, brand, printer and installer accounts. The mail outbox and stuck drafts need a role with no place limit. Password resets and restaurant owner recovery need the platform owner or central operations with no place limit. Restaurant setups with no known city are hidden from managers limited to a place.
    Why:
    Admin changes other people's records, so it is limited to operational roles and their place.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they make the change, or you ask an issuer for the role you need.
  • Workboard: you see and change only leads in your own place

    Allowed:
    Any staff role opens the workboard. Assigning, follow-ups and recording contact permission need a role that can edit: platform owner, central operations, managers and sales/BNI coordinators. Finance and QA reviewers can only read.
    Refused:
    Leads outside your place are not shown. A lead with no city, including every BNI introduction, needs a role with no place limit. You can only assign a lead to someone whose role covers it.
    Why:
    Leads hold personal contact details.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they set the city or pass the lead to someone who covers it.
  • A contact denial is one-way; only a platform owner covering that lead can reverse it

    Allowed:
    Anyone who can edit a lead records permission as granted or not granted, with a basis (up to 120 characters) and evidence (up to 500). Not granted moves the lead to suppressed. A platform owner whose own owner role covers the lead's city or area can reverse a denial with a reason (up to 300 characters); a lead with no city needs an owner role with no place limit. The reversal is recorded against the owner's account with the reason.
    Refused:
    Everyone else, including central operations and managers, cannot reverse a denial. An owner role for another city does not count, even with a manager role for the lead's city: platform owner (Mumbai) plus city manager (Raipur) cannot reverse a Raipur lead. Recording permission never sends a message.
    Why:
    A refusal to be contacted must stick.
    If you need it done:
    Next actor: a platform owner whose role covers the lead's place. Next action: they review the new evidence and record the reversal with it as the reason.
  • Do-not-contact (suppression) entries are add-only, except unverified /unsubscribe entries

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators add an email address with a reason (up to 500 characters); who added it is recorded. Recipients can add their own address on /unsubscribe; it takes effect at once and is recorded as an unverified entry. The same outreach staff may lift an unverified /unsubscribe entry with a reason (10 to 500 characters), for example when the owner of the address asks in writing to receive promotional email again. The lift records who lifted it, when, why and what the entry was. When outreach staff add an address that already has an unverified /unsubscribe entry, that entry becomes a permanent staff entry, recorded with who added it and why.
    Refused:
    Finance and QA reviewers and all restaurant, brand, printer and installer accounts cannot add or lift entries. Entries added by staff, and entries recorded before unverified entries were tracked, can never be lifted. A suppression and a lead's contact denial are separate: record both where both apply.
    Why:
    An opt-out must never be quietly reversed; only an entry nobody verified can be lifted, and only on the record.
    If you need it done:
    Next actor: one of the outreach staff named above. Next action: they add the address, or lift an unverified /unsubscribe entry with a reason (POST /api/suppressions/lift).
  • Inbound enquiry permission is specific; drafts, reminders and imports are not permission

    Allowed:
    Follow-ups, assignments, reminders and imports are internal records only.
    Refused:
    An enquiry submitted on /enquiry or the guided form records permission to respond to that enquiry, with source and timestamp; there is no separate opt-in. An existing denial, do-not-contact stage or suppressed address is not reopened by submission. The receipt is queued when an email is supplied, subject to identity and rate limits, and suppressed addresses cannot receive it. No feature sends promotional outreach email or WhatsApp. Imported leads start with permission unknown. BNI membership is not consent. Do not import scraped or gated-directory contacts. Decision: 5 October 2026.
    Why:
    A person's own submitted enquiry documents their request for an enquiry-specific reply, not promotional permission. Imports and drafts do not document that request.
    If you need it done:
    Next actor: the lead owner. Next action: check existing denial and suppression before responding to an inbound enquiry; for imported leads, record documented permission before one-to-one contact outside the platform.
  • Lead import: every row must be in a city you can edit

    Allowed:
    Paste CSV, preview, then commit. Only you can commit your preview, within 30 minutes.
    Refused:
    Rows in cities you cannot edit are left out (finance and QA reviewers cannot edit, so all their rows are left out). Duplicates are checked against all leads, including ones you cannot see. If your role changes between preview and commit, the commit is refused.
    Why:
    Import creates personal-data records under the same place rule as manual edits.
    If you need it done:
    Next actor: a colleague who covers the left-out rows, or central operations. Next action: give them only those rows.
  • Lead export: only some roles, only for their own place

    Allowed:
    Platform owner, central operations, managers and finance reviewers export leads for a city they cover. Exporting every city needs a role with no place limit.
    Refused:
    Sales/BNI coordinators and QA reviewers cannot export. "Export my leads" shows only leads you can export, which may be none.
    Why:
    Exporting copies personal data out of the platform.
    If you need it done:
    Next actor: your city manager or central operations. Next action: they run the export.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • Finance review: read, export and review in your place; you do not record settlements

    Allowed:
    A finance reviewer reads and exports statements for its place, reviews reconciliations (reason of at least 10 characters), approves obligations with no open dispute, and can record a sale event for an agreement it covers. Sale events are stored unverified and create nothing payable until a verified sales source is approved.
    Refused:
    Recording settlements (central operations or the platform owner do that), editing the workboard and opening /admin. Nobody reviews a reconciliation they submitted, and nobody who is a member of the restaurant or brand on the agreement reviews its reconciliations or approves its monthly obligations. Nobody approves a disputed monthly obligation after resolving one of its disputes, and nobody resolves a reconciliation dispute they opened or that concerns an agreement of an organisation they belong to.
    Why:
    Finance review checks recorded money; it is not where payment is recorded, and a payable decision needs a reviewer independent of both parties.
    If you need it done:
    Next actor: central operations (settlements), or another finance reviewer, central operations member or platform owner covering the agreement who did not submit it, did not resolve its dispute and belongs to neither party. Next action: pass the item to them.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.

Next actor and action: Next actor: independent approver or disputed counterparty. Next action: record a supported review outcome, or leave the item held/disputed with a named follow-up.

Internal role

Quality reviewer

qa_reviewer

Independently review eligible installation evidence; cannot review work where the reviewer is a member of the installer or venue organisation.

Start and setup

Accept an internal invitation and sign in with your password; check for organisation conflict before opening the review queue.

What to prepare

  • Internal grant and permitted scope
  • Evidence plus restaurant acknowledgement
  • Conflict check and review outcome

Who grants access

An authorized issuer grants this role. QA is separate from operations; conflicted reviewers must not approve their own organisation's work.

Limits and gotchas

  • The /admin surface does not admit qa_reviewer. The venue installation-jobs board is party-scoped and returns no jobs for a QA-only reviewer; use the dedicated QA board.
  • Installer self-report alone is insufficient. QA approval does not trigger automatic payment; settlement remains separate and manual.

Rules and limits you should know before you start

  • Each role is checked on its own; holding several roles never combines them

    Allowed:
    You may hold several roles at once. An action is allowed when one of your roles, by itself, permits it and covers the record.
    Refused:
    One role's permission never borrows another role's city or organisation. Example: platform owner for Mumbai plus city manager for Raipur does not make you a platform owner for Raipur. Example: a finance reviewer role plus an area manager role for Bandra does not let you edit records outside Bandra.
    Why:
    Each role was issued for a specific scope and is audited that way.
    If you need it done:
    Next actor: the person who issues roles in your organisation (for staff: the platform owner or central operations). Next action: issue one role of the right kind that covers the record.
  • A role for a place covers that place and what is inside it, never a neighbour

    Allowed:
    A country role covers its cities and areas, a city role its areas, an area role only that area. A role with no geography limit covers every location of its own organisation; for platform owner and central operations it is platform-wide.
    Refused:
    Records in another city or area, and records whose location is unknown, are refused. A platform owner or central operations role limited to a city is limited like any other role.
    Why:
    Access follows the structured location of the record, never a city name in a link or address.
    If you need it done:
    Next actor: the person who issues roles. Next action: issue a role for the right place, or pass the record to a colleague who covers it. A record with no city needs central operations, through /contact to set the city first.
  • A role works only while your membership of its organisation is active

    Allowed:
    A role works while it is not revoked or expired and you are an active member of the same organisation.
    Refused:
    When your membership ends, every role you held in that organisation ends with it, recorded, and stops on your next action. Joining the same organisation again never brings an old role back: you hold only the roles given after you rejoin. A staff role (for example platform owner) held in a restaurant, brand, printer or installer organisation gives no authority.
    Why:
    Membership and roles are separate audited records; both must be current.
    If you need it done:
    Next actor: an owner of your organisation, or central operations for staff. Next action: invite you again (staff accept a new platform invitation). Signing out and in does not restore access.
  • Signing in, a link or this guide never gives access to someone else's records

    Allowed:
    Each page re-checks your role when you open it. A signed-in account can create its own organisation (for example a brand or printer organisation) and becomes its owner.
    Refused:
    An enquiry creates no account or role. An installer application creates a person, an installer organisation and an owner role for that organisation, but no sign-in. A copied link, a guessed ID or a page for another city shows a refusal or nothing.
    Why:
    Every page checks the role held on the server, not what the screen shows.
    If you need it done:
    Next actor: the person who invited you, or central operations, through /contact. Next action: ask for access to the exact organisation or place you need.
  • Sign-in, invitation and reset links have fixed limits

    Allowed:
    A session lasts up to 30 days on the device you signed in on. An invitation works once, for 72 hours, only with the email address it was sent to. A password reset link works once, for 30 minutes.
    Refused:
    After 5 failed sign-ins for one email (or 30 from one network) within 15 minutes, sign-in pauses until the count drops. A new invitation to the same email for the same organisation cancels the earlier unused one; a new reset link cancels the earlier one. There is no self-service "forgot password". Sign-in needs JavaScript. Any change (a form or button that saves, sends or removes something) is refused with a 403 when your browser reports it was sent from another website, including another putyourbrand.in subdomain; nothing is changed, and reloading the page on putyourbrand.in and trying again works.
    Why:
    Short-lived, single-use links limit the damage if a link is forwarded.
    If you need it done:
    Next actor: the person who invited you (new invitation), or central operations or the platform owner (password reset after an identity check; a platform owner's reset needs another platform owner). Next action: ask through /contact.
  • An authenticator is required only for the platform owner

    Allowed:
    Every other account signs in with a password. Anyone may add an authenticator at /account/security.
    Refused:
    Staff who add an authenticator are then asked for its code at every sign-in. Recovery codes work only at that sign-in code step: typed anywhere else they are refused and stay valid. Restaurant, brand, printer and installer accounts are never asked for a code at sign-in, so their recovery codes cannot be used. Signing in with a recovery code signs out other sessions and asks for a new authenticator within 15 minutes.
    Why:
    Owner decision of 3 October 2026; an authenticator once added is never silently switched off.
    If you need it done:
    Next actor: the platform owner. Next action: if you lost your authenticator and cannot use a recovery code, ask through /contact for an identity-verified reset; nobody can reset their own.
  • A date you enter means that whole day in India Standard Time

    Allowed:
    "Valid until 15 October" means until 23:59:59 IST on 15 October; a start date starts at 00:00 IST.
    Refused:
    For offer expiries, quote validity, print deadlines and staff role expiry, a date before today (IST) or a time already passed is refused. For sellable periods, only a period whose last day has passed is refused. Your device's time zone is ignored.
    Why:
    Every venue and partner today is in India.
    If you need it done:
    Next actor: you. Next action: choose today or a later date; if a deadline must end at a set hour, say so in the note.
  • A PutYourBrand staff account never joins, owns or accepts terms for a restaurant

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators may start an audited assisted onboarding and prepare steps the owner reviews. Finance and QA reviewers cannot.
    Refused:
    An account with any staff role, or a putyourbrand.in email address, cannot be added to a restaurant or accept its agreement, even if it also holds that restaurant's owner role.
    Why:
    Acceptance must come from the restaurant itself.
    If you need it done:
    Next actor: the restaurant owner, on an account with no staff role. Next action: they accept, or add their own non-staff person. Former staff ask central operations to end their staff roles first.
  • Staff roles: who may give which role, where

    Allowed:
    The platform owner, central operations and country, city and area managers give staff roles. Ranks: platform owner 100; central operations, QA reviewer, finance reviewer 90; country manager 60; city manager 40; area manager and sales/BNI coordinator 20. You may give a role of your rank or lower, for a place equal to or inside your own.
    Refused:
    A higher-ranked role; a wider place; a role with no place limit (unless you are platform owner or central operations with no limit); a role for yourself; a role for someone who is not a member of the platform organisation; an expiry that is not in the future. One of your roles must cover all of this by itself.
    Why:
    It stops a manager from choosing who reviews their own work, and stops authority growing beyond what was given.
    If you need it done:
    Next actor: an issuer of equal or higher rank who covers the place (a platform owner for platform owner roles). Next action: they give the role; the person must have accepted a platform invitation first.
  • Staff roles: ending a role takes effect at once, within your rank and place

    Allowed:
    An issuer may end a staff role of equal or lower rank inside their own place. It stops on the holder's next action and is audited with who ended which role and when.
    Refused:
    Ending your own role; ending a higher-ranked role (central operations cannot end a platform owner role); ending a role with no place limit, or outside your place, unless you are platform owner or central operations with no limit.
    Why:
    Roles must be removable quickly, but only by someone who could have given them.
    If you need it done:
    Next actor: central operations (a platform owner for platform owner roles). Next action: they end the role on the Team page.
  • Admin is for the platform owner, central operations and country, city and area managers

    Allowed:
    Those roles open /admin. A manager limited to a place sees and acts on records in that place only.
    Refused:
    Sales/BNI coordinators, finance and QA reviewers and all restaurant, brand, printer and installer accounts. The mail outbox and stuck drafts need a role with no place limit. Password resets and restaurant owner recovery need the platform owner or central operations with no place limit. Restaurant setups with no known city are hidden from managers limited to a place.
    Why:
    Admin changes other people's records, so it is limited to operational roles and their place.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they make the change, or you ask an issuer for the role you need.
  • Workboard: you see and change only leads in your own place

    Allowed:
    Any staff role opens the workboard. Assigning, follow-ups and recording contact permission need a role that can edit: platform owner, central operations, managers and sales/BNI coordinators. Finance and QA reviewers can only read.
    Refused:
    Leads outside your place are not shown. A lead with no city, including every BNI introduction, needs a role with no place limit. You can only assign a lead to someone whose role covers it.
    Why:
    Leads hold personal contact details.
    If you need it done:
    Next actor: central operations, through /contact. Next action: they set the city or pass the lead to someone who covers it.
  • A contact denial is one-way; only a platform owner covering that lead can reverse it

    Allowed:
    Anyone who can edit a lead records permission as granted or not granted, with a basis (up to 120 characters) and evidence (up to 500). Not granted moves the lead to suppressed. A platform owner whose own owner role covers the lead's city or area can reverse a denial with a reason (up to 300 characters); a lead with no city needs an owner role with no place limit. The reversal is recorded against the owner's account with the reason.
    Refused:
    Everyone else, including central operations and managers, cannot reverse a denial. An owner role for another city does not count, even with a manager role for the lead's city: platform owner (Mumbai) plus city manager (Raipur) cannot reverse a Raipur lead. Recording permission never sends a message.
    Why:
    A refusal to be contacted must stick.
    If you need it done:
    Next actor: a platform owner whose role covers the lead's place. Next action: they review the new evidence and record the reversal with it as the reason.
  • Do-not-contact (suppression) entries are add-only, except unverified /unsubscribe entries

    Allowed:
    The platform owner, central operations, managers and sales/BNI coordinators add an email address with a reason (up to 500 characters); who added it is recorded. Recipients can add their own address on /unsubscribe; it takes effect at once and is recorded as an unverified entry. The same outreach staff may lift an unverified /unsubscribe entry with a reason (10 to 500 characters), for example when the owner of the address asks in writing to receive promotional email again. The lift records who lifted it, when, why and what the entry was. When outreach staff add an address that already has an unverified /unsubscribe entry, that entry becomes a permanent staff entry, recorded with who added it and why.
    Refused:
    Finance and QA reviewers and all restaurant, brand, printer and installer accounts cannot add or lift entries. Entries added by staff, and entries recorded before unverified entries were tracked, can never be lifted. A suppression and a lead's contact denial are separate: record both where both apply.
    Why:
    An opt-out must never be quietly reversed; only an entry nobody verified can be lifted, and only on the record.
    If you need it done:
    Next actor: one of the outreach staff named above. Next action: they add the address, or lift an unverified /unsubscribe entry with a reason (POST /api/suppressions/lift).
  • Inbound enquiry permission is specific; drafts, reminders and imports are not permission

    Allowed:
    Follow-ups, assignments, reminders and imports are internal records only.
    Refused:
    An enquiry submitted on /enquiry or the guided form records permission to respond to that enquiry, with source and timestamp; there is no separate opt-in. An existing denial, do-not-contact stage or suppressed address is not reopened by submission. The receipt is queued when an email is supplied, subject to identity and rate limits, and suppressed addresses cannot receive it. No feature sends promotional outreach email or WhatsApp. Imported leads start with permission unknown. BNI membership is not consent. Do not import scraped or gated-directory contacts. Decision: 5 October 2026.
    Why:
    A person's own submitted enquiry documents their request for an enquiry-specific reply, not promotional permission. Imports and drafts do not document that request.
    If you need it done:
    Next actor: the lead owner. Next action: check existing denial and suppression before responding to an inbound enquiry; for imported leads, record documented permission before one-to-one contact outside the platform.
  • Lead import: every row must be in a city you can edit

    Allowed:
    Paste CSV, preview, then commit. Only you can commit your preview, within 30 minutes.
    Refused:
    Rows in cities you cannot edit are left out (finance and QA reviewers cannot edit, so all their rows are left out). Duplicates are checked against all leads, including ones you cannot see. If your role changes between preview and commit, the commit is refused.
    Why:
    Import creates personal-data records under the same place rule as manual edits.
    If you need it done:
    Next actor: a colleague who covers the left-out rows, or central operations. Next action: give them only those rows.
  • Lead export: only some roles, only for their own place

    Allowed:
    Platform owner, central operations, managers and finance reviewers export leads for a city they cover. Exporting every city needs a role with no place limit.
    Refused:
    Sales/BNI coordinators and QA reviewers cannot export. "Export my leads" shows only leads you can export, which may be none.
    Why:
    Exporting copies personal data out of the platform.
    If you need it done:
    Next actor: your city manager or central operations. Next action: they run the export.
  • Operations staff can pause offers, print orders, installation jobs and campaign links in an area

    Allowed:
    A pause cancels nothing already recorded.
    Refused:
    While a pause covers the area, the paused action is refused and nothing is saved: making, countering or accepting offers; choosing a quote or confirming a print order; offering or accepting installation jobs. Resuming needs written evidence.
    Why:
    A pause is the emergency brake for a market with a known problem.
    If you need it done:
    Next actor: central operations, through /contact. Next action: ask when the pause will be lifted, then retry.
  • QA: decide only evidence you are independent of, after the venue acknowledges it

    Allowed:
    A QA reviewer covering the location accepts, partly accepts (at least one unit) or asks for rework (reason of 3 to 500 characters) once the restaurant has acknowledged the evidence. The QA board lists jobs for QA reviewer roles; central operations and the platform owner can also decide.
    Refused:
    Anyone who belongs to the job's installer or venue organisation, and the person who gave the venue acknowledgement. Evidence not yet acknowledged. After a rejected sign-off, only rework. A QA decision pays nothing by itself. If the job is disputed, the person who made its QA decision or gave its venue acknowledgement cannot resolve the dispute.
    Why:
    Payable work needs two different people to confirm it.
    If you need it done:
    Next actor: another QA reviewer, central operations member or platform owner who is independent of the job. Next action: they decide it.
  • No money moves through this platform

    Allowed:
    Agreements record the agreed terms. After installer earnings or printer obligations are paid outside the platform, central operations or the platform owner record the settlement with a reference.
    Refused:
    No checkout, card payment, automatic invoice, transfer or payout. Payments between brands and restaurants are not recorded here. Pay-per-sale terms are off until a verified sales source is approved. INR 800 per table is an onboarding reference, not a complete contract.
    Why:
    Payments are manual by decision.
    If you need it done:
    Next actor: the parties, then central operations, through /contact for installer or printer payments. Next action: pay outside the platform, then ask for the settlement to be recorded.
  • Evidence: the installer sends it, the restaurant owner acknowledges, someone else decides QA

    Allowed:
    The accepting installer sends 1 to 20 PNG or JPEG photos (up to 10 MB each). The sign-off link is shown once to the installer, who gives it to the restaurant. The restaurant owner (or central operations or the platform owner) acknowledges through it. QA review follows.
    Refused:
    Restaurant operators and managers cannot acknowledge. Keep the sign-off link: it is not shown again. The person who acknowledged cannot also make the QA decision. One dispute at a time per job; only central operations or the platform owner resolve it, and never the person who made the job's QA decision or gave its venue acknowledgement.
    Why:
    Payable work needs two different people to confirm it.
    If you need it done:
    Next actor: the restaurant owner, then an independent QA reviewer. Next action: acknowledge from the link, then QA decides.

Next actor and action: Next actor: independent QA reviewer for eligible evidence, or the installer/venue for requested correction. Next action: record a reasoned review or return the evidence with a specific next step.

Restaurant wizard clarification

Step 4 selects a diner offer

The wizard step 4 uses listActivatableDinerOffers to show eligible diner offers for the restaurant experience. This is not the venue baseline advertiser offer used when an advertiser proposes placement terms. A diner offer is approved by the venue restaurant owner or global platform_owner/central_operations role, not by the brand owner. Campaign activation is a separate brand/platform decision. The wizard requires both an active market campaign and an approved diner offer.

Campaigns are created and submitted by any brand member on the brand workspace (/dashboard/brands); the brand owner or central operations activates them, and activation needs a destination web address the brand owner (or central operations) has approved. A restaurant cannot create a brand campaign from the wizard: when no campaign is active in its market, the next actor is a brand advertising there, and our team can be asked on /contact. The restaurant creates its own starting offer inline in wizard step 4 or on /dashboard/venues/[location]/offers; the venue owner or central operations approves it.

For existing or stuck drafts

Staff assistance is not participant acceptance

Authorized platform-owner or central-operations staff with platform-wide access can use the Admin Onboarding workspace to assist an existing or stuck draft only within their authorized platform-wide scope. The command requires recorded participant consent, a reason, a preview of proposed changes and explicit confirmation. It records the assisting staff actor. It cannot mark identity verified or accept an agreement for the participant; the real authorized participant must complete those steps. A staff-only wizard binding does not establish a restaurant participant: step 1 is refused before creating an organisation. Only the participant bound to a valid wizard may complete step 1; authorized staff can explain the process or assist a generic draft through the separate audited workflow, but cannot complete the participant-bound ownership step. A staff-bound or legacy wizard has no in-app ownership repair or rebind path. This access proof is not independent legal identity verification.

Next actor: the bound participant must complete step 1 in their existing valid wizard. For a staff-bound or legacy wizard, the platform team must review the case; this application currently has no in-app repair or rebind control, so staff must not start another ownership claim inside that wizard. The participant must supply any missing facts directly; if staff cannot see a generic draft, an authorized platform-wide issuer must first resolve access scope.