Downloads Ignite Global Support Home Start a conversation Sign in
Start a conversation
  1. StreetSmart
  2. StreetSmart Articles
  3. Articles

StreetSmart “Add Device” Authorization Error: Requester Email Not Recognized as Admin/Super User

Contents

Overview

When adding one or more device phone numbers to a StreetSmart account, the provisioning workflow can fail due to an authorization mismatch, even if the operation status appears successful (for example, adddevice_action is completed.).

This occurs when the email address used to submit the request is not recognized by StreetSmart as an Admin/Super User for the specified company/account (for example, due to an email mismatch/alias or missing admin mapping in the backend).

Solution

Symptoms / Error Message

The key authorization error message is:

Processed by Internal Lambda : User email <requester_email> is not set as an Admin for companyID <company_id>.

In some cases, you may also see a status message such as:

adddevice_action is completed.

If the private authorization message indicates the requester email is not an Admin/Super User for the company ID, the device is not actually added.

Cause

This is expected behavior when the requester’s email address is not recognized in StreetSmart as an Admin/Super User for the target company/account. No product defect is indicated by this message; it is an authorization/provisioning mismatch.

1) Confirm the requester is an Admin/Super User and the email matches

  1. Sign in to the StreetSmart web portal (for example: https://your_instance.domain.com).
  2. Go to Administration → Users.
  3. Locate the requester’s user record and open Edit User.
  4. Verify:
    • The email / notification email field matches the email used to submit the provisioning request (watch for typos, aliases, or formatting differences).
    • The user is assigned an Admin/Super User role as intended.

If the user is not recognized as an Admin/Super User for the company/account in the backend record, submit the request from an email that is already recognized as an Admin/Super User, or request that the admin authorization mapping be validated/updated per your organization’s policy.

2) After provisioning: verify the device is visible in the portal

  1. Go to Administration → Devices.
  2. If you do not see the device(s), adjust the Group filter on the left and select ALL Groups (devices can appear “missing” when the portal is scoped to only certain groups).
  3. Confirm each newly added phone number appears in the list and is associated to the intended user/worker.

3) (Optional) Adjust the user’s Group or Security Role

If the user needs to be placed in a different group or role:

  1. Go to Administration → Users.
  2. Open the relevant user and select Edit User.
  3. Update Group and/or Security Role as needed.

4) Activate the phone in the StreetSmart mobile app

  1. In the portal, retrieve the worker’s PIN from the user record (Administration → Users).
  2. On the phone, open the StreetSmart mobile app and activate using:
    • the phone number, and
    • the worker PIN.
  3. Return to Administration → Devices and confirm the device shows as activated (for example, the Activated Date is populated once activation is complete).

Manual Provisioning (If Authorization Continues to Block the Request)

If the authorization mismatch cannot be resolved immediately (for example, due to backend admin mapping), the device phone numbers may need to be added via a manual provisioning process. After manual provisioning, validate device visibility and complete activation using the worker PIN.

Validation Checklist

  • The device phone number(s) appear under Administration → Devices.
  • If initially missing, selecting ALL Groups in the group filter reveals the device(s).
  • The device is linked to the intended user/worker.
  • After mobile activation, the portal reflects activation status (for example, Activated Date populated).

Frequently Asked Questions

1. How do I know I’m hitting the same authorization problem?

You will see the exact message:

Processed by Internal Lambda : User email <requester_email> is not set as an Admin for companyID <company_id>.

This indicates the requester email is not recognized as an Admin/Super User for that company/account, so the device add will not complete.

2. The Devices page doesn’t show the newly added phone number. Does that mean it wasn’t added?

Not always. First set the Devices page group filter to ALL Groups. Devices can appear “missing” if only a subset of groups is selected.

3. How can I confirm whether my email is correctly tied to my StreetSmart admin account?

In the web portal, go to Administration → Users, open your user, and select Edit User. Verify the email/notification email field is correct and matches the email used to submit provisioning requests.

4. The device is listed under Administration → Devices, but it isn’t active yet—what’s next?

Retrieve the worker PIN from Administration → Users, then activate the StreetSmart mobile app on the phone using the phone number + PIN. After activation, the portal should reflect activation status (for example, Activated Date populated).

5. What should I provide if the authorization error persists even though I’m an Admin/Super User?

Provide:

  • The exact error message (verbatim).
  • The <company_id>.
  • The requester email as shown in StreetSmart (from Edit User).
  • The phone number(s) to be added.

This helps identify whether the issue is an email mismatch/alias or an admin-authorization mapping problem in the backend.

Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted

Comments