Team access
Sign in
Use the email address your team invited. Don't have access yet? Ask your team administrator for an invitation.
You were signed out or your session ended. After you sign in you return to the page you asked for.
Takes about a minute.
Guide for this pageSign in to your team workspaceHide guideShow guide
Who this page is for: Anyone who already accepted an invitation (platform staff, restaurant, brand, printer and installer accounts). There is no self-registration here: if you have never accepted an invitation, you have no account yet.
Time required: About a minute.
Rules and limits you should know before you start
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.
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.
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.
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.
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.
Every rule for each role, with the reason behind it, is on the Docs page under Rules and limits.
Have ready before you start
- The email address and password you chose when you accepted your invitation.
- Your phone with the authenticator app, if your account holds the platform owner role, or holds an internal staff role and you have set up an authenticator; a six-digit code is then asked for after the password. Other accounts, including restaurant, brand, printer and installer accounts, sign in with the password only.
- Your one-time recovery codes only if your authenticator is lost.
Steps
- Enter your email and password and choose Sign in.
- If a code step appears, enter the current six-digit code from your authenticator app.
- You are taken to your workspace, or back to the page you were trying to open.
After you submit: who acts next
A session opens on this device only. Every page you open re-checks your role and scope; signing in does not by itself grant access to any organisation or location.
Common mistakes to avoid
- Using a recovery code signs you in once and signs out every existing session, but the sign-in challenge is available only to accounts that are asked for a code at sign-in (the platform owner, and internal staff who have set up an authenticator). Those users are taken to /account/security to set up a new authenticator in that same session within 15 minutes of sign-in. Other accounts do not receive this challenge. Next actor for those accounts, or for accounts with no unused codes: the platform owner. Next action: contact the platform owner through /contact to request an audited identity-verified reset.
- Waiting too long on the code step: it expires 5 minutes after the password is accepted; choose Start again.
- Expecting a password-reset email: email delivery is not enabled yet; ask your administrator for a secure reset link.
Where to get help
Only the platform owner role requires an authenticator. If the platform owner account has none enrolled and cannot complete set-up, the authorised VPS operator must start owner recovery. For account, access or data problems, contact central operations through the Contact page; the support channels are shared with other DATCRAZY LLP services, so say the message is about PutYourBrand. No reply time is promised and the Contact page is not a formal-notice channel.
Email delivery is not enabled yet. Ask your administrator for a secure invitation or reset link.
