Forum Discussion

KlaudiaWEQS's avatar
KlaudiaWEQS
Cloud Apps
07-21-2025

Unable to change system settings [403 Forbidden error]

Hey, 

we are unable to update any system settings on our account on our Sisense instance - keep getting 403 Forbidden error from any post requests made to the settings endpoint e.g. api/v1/settings/system.

We're particularly interested in updating our CORS Origins Allowed domains.

What could be the reason and how could we handle this issue?

6 Replies

  • DRay's avatar
    DRay
    Sisense Employee

    Hello KlaudiaWEQS​,

    Thank you for reaching out.

    The 403 Forbidden error you are encountering when making POST requests to the settings endpoint, such as api/v1/settings/system, could be due to insufficient permissions or incorrect configuration in your Sisense instance.

    1. Permissions Issue: Ensure that the account you are using to make these API requests has the necessary permissions to update system settings. This might involve checking the roles and permissions assigned to the user or API token being used.
    2. CORS Configuration: To update the CORS Allowed Origins, you can use the Sisense UI by navigating to Admin > Security & Access > Security Settings > General, and then add your application's domain to the CORS Allowed Origins list. This is a recommended approach to manage CORS settings directly through the UI 1.
    3. REST API Usage: If you prefer using the REST API to add new domains to the CORS settings, ensure that the API endpoint is correctly configured and that the API token or user account has the appropriate permissions to make such changes. The REST API supports adding domains and even using wildcards to cover a range of domains 2.

    By addressing these potential issues, you should be able to resolve the 403 error and update your CORS settings successfully. If the problem persists, consider reviewing the API documentation or reaching out to Sisense support for further assistance.

  • Thank you for the quick response!

    In our case, we're using a full admin role, and the token appears to be valid. However, we're still unable to update any settings—neither through the UI nor via the REST API.

    If I understand correctly, the next step would be to reach out to Sisense support?

    • DRay's avatar
      DRay
      Sisense Employee

      Hi KlaudiaWEQS​,

      Yes, at this point I recommend reaching out to support. They can gather logs and perform more in-depth troubleshooting than we can here. Once they get it resolved I would love to hear what the solution was! I'm just curious. 😃