This procedure is only needed for subscriptions older than June 24 2021, where the organization roles have not been added automatically at subscription time.

For new subscriptions, this is not necessary and the team members added to your organization can access by default the Things solutions resources by API (e.g. create connections, namespaces, etc.),
if they authenticate with a SuiteAuth token comprising their organization role. See example Create a Suite Auth client for an organization rile.

Precondition

You are the user who provisioned the subscription.

Get your solution policy

Open the Bosch IoT Things UI.
Copy the API token.
Copy the policy ID of your Things instance.
Open the apidocs > Bosch IoT Things > Policy
Authenticate with the API token from step 2, and check the box for the Bosch ID authorization.
Open the section GET /policies/{policyId}
Click Try it out to get access to the entry fields.
Set the policyId of your service instance from step 3.
E.g. com.bosch.iot.things.solution:you-solution-id
Execute.

If the DEFAULT part misses the subjects with your organization roles, you can add them manually.

"subjects": {
        "iot-suite:/organization.<org-guid>.Owner": {
          "type": "generated"
        },
        "iot-suite:/organization.<org-guid>.Developer": {
          "type": "generated"
        },
        "iot-suite:/organization.<org-guid>.Manager": {
          "type": "generated"
        }
}

Change a part of the solution policy

Navigate to PUT /policies/{policyId}/entries/{label}/subjects/{subjectId}
Click Try it out to get access to the entry fields.
Set the policyId to the ID from above.
Set the label to DEFAULT.
Set the subjectId to the role
Use the exact notation how you see it at https://accounts.bosch-iot-suite.com/oauth2-clients/ when you try to create a client "iot-suite:/organization.xxx.Developer"
Set the type in the Request body.

{

"type": "team-developer-role"

}
Execute.