Secure Your Account

General security hygiene for all StoreFulfil users.

Updated Aug 2026

Use this at sign-in, on shared terminals, and whenever an account or session looks unexpected.

Where to start

Settings → Account

What you will see

Use your own account settings for personal security and language preferences. Credentials are hidden in this example.

StoreFulfil handles sensitive PII. Basic security hygiene must be maintained.

Best Practices

  1. Use strong, unique passwords for all accounts.
  2. Ensure browsers are kept up to date.
  3. Log out of shared terminals when not actively supervising them.

Protect the session

  1. Use your own account and password.
  2. Work only within the displayed client scope.
  3. Sign out when leaving a shared terminal.
  4. Report an unexpected role, client, password change, or session without sharing the secret.

Questions and hand-off

If The session is lost during work

Sign in again and reopen the current record before continuing.

If You suspect someone used the account

Stop work, report the time and visible symptom to an Admin, and do not send passwords or tokens.

What happens next

The work is either resumed from a fresh session and current record or handed to an Admin with only safe references.

Check your result

User accounts remain secure.

Admin details: states, evidence and hand-off

Owner: Technical Support. Area: Security. Action owner: Each signed-in Warehouse Operator, Warehouse Admin, or Brand User.

What you might see

Normal session

The signed-in person is working within the intended role and client scope.

Next: Use only the data needed for the current task and sign out of shared terminals.

Suspicious access

A password, session, role, or client scope may have been exposed or changed unexpectedly.

Next: Stop sharing access, report the visible facts to an Admin, and follow the account response.

Session finished

The user no longer needs the terminal or account open.

Next: Sign out and remove any temporary working notes or downloaded data.

Completion evidence

  • The user is signed out when finished and any suspected access issue has an owner.

When to ask for help

  • Record the account or role, time, visible symptom, and affected scope; never include secrets.
Before you start

Give every signed-in user a short, practical routine for protecting access and customer shipping information.

  • The user can access their own sign-in account.
  • Shared terminals and browsers are identified.
  • The user knows the approved route for reporting suspected access.

© 2026 STOREFULFIL PTY LTD (ACN 701 718 649 · ABN 98 701 718 649), Queensland, Australia · StoreFulfil Operations Library.