There are four types of 403 errors as shown below.
This article will go into further detail on the first two.

ERROR MESSAGE	REASON/s
Error on creating run Error: Request failed with status code 403	Your workspace is on a free plan and have reached the limit of 2 active runs.
403 Forbidden - Whoops, looks like you don't have access to this page.	You lack the necessary permissions or privileges to access the page or feature.
403 app_not_configured 403 app_not_configured_for_user 403 app_not_enabled_for_user	These are Security Assertion Markup Language (SAML) app error messages. Click here for troubleshooting
HTTP error: status code 403	This could be caused by an external factor. Contact Qase support chat for help.

A) "Error on creating run Error: Request failed with status code 403"

On the Free Plan, you can only have two active runs. If you already have two running and try to start another one (even through API), it will provide this error. You'll need to Delete, Complete, or Abort one of the ongoing runs first.

You'll have to review your other projects since the limit is applied on the workspace level, not just on a single project. This can also include archived projects.

B) "403 Forbidden - Whoops, looks like you don't have access to this page."

Not enough permissions can lead to these issues:

Can't enter the Workspace
Can't access the Project
Limited access to certain features based on your plan
No access to the Billing section
Only access is to the Billing section
Can't configure workspace settings
Can't configure integrations
Can only view or comment in the workspace

For situations 4-8, visit this link to verify your user type and role: https://app.qase.io/workspace?page=1

SCENARIO	SOLUTION
1. Can't enter the workspace	There's another active session with different credentials. Log out of all sessions before attempting to log in again with the correct workspace credentials.
2. Can't access the Project	Ask the workspace owner to check the Project Settings and give you access.
3. Limited access to certain features based on your plan	Check which plan you have and review the features: Free, Startup, Business or Enterprise
4. No access to the Billing section	Only owners, billing users and administrators with billing permissions can access the Billing Section. Reach out to them to request billing permissions.
5. Only access is to the Billing section	As a a billing user, you can only view the Workspace: Billing section and not other entities. Contact the workspace owner or admin to change this.
6. Can't configure workspace settings	Check if you are a read-only user or if you don't have admin permissions. Both limit your ability to configure workspace settings. If you're already an Admin, check for any removed permissions in your customized role.
7. Can't configure integrations	First, check if the person that created the API token being used has sufficient permissions in Qase. (Regular license and Administrator role) Next, ensure you have Admin rights for the app you're integrating. API tokens inherit issuer's permissions. If the issuer lacks admin permissions, you will get a 403 error.
8. Can only view or comment in the workspace	A user with a read-only license is limited to viewing and commenting, regardless of their role. To perform other actions, you must first be switched to a regular license.

I cannot access a feature or option inside qase?

How do I fix a 403 error?

A) "Error on creating run Error: Request failed with status code 403"​

B) "403 Forbidden - Whoops, looks like you don't have access to this page."

A) "Error on creating run Error: Request failed with status code 403"