How do I resolve permission errors when logging a run?

Permission errors when logging a run typically indicate a mismatch between your code, your credentials, or your deployment configuration and the W&B entity you’re trying to log to. This page lists the most common causes and how to address each one so that your run can write to the intended entity and project. To resolve permission errors when logging a run to a W&B entity, work through the following checks:

Verify entity and project names: Ensure correct spelling and case sensitivity of the W&B entity and project names in your code. A typo or case mismatch causes the run to target a location you don’t have access to.
Confirm permissions: Ensure the administrator has granted you the necessary permissions for the target entity and project.
Check log-in credentials: Confirm that you’re logged in to the correct W&B account. Test by creating a run with the following code, replacing [ENTITY-NAME] and [PROJECT-NAME] with your target entity and project:
```
import wandb

run = wandb.init(entity="[ENTITY-NAME]", project="[PROJECT-NAME]")
run.log({"example_metric": 1})
run.finish()
```
Set API key: Set the WANDB_API_KEY environment variable so the client authenticates with the intended account. Replace [API-KEY] with your W&B API key:
```
export WANDB_API_KEY="[API-KEY]"
```
Confirm host information: For custom deployments, point the client at the correct W&B host so the run is sent to the right server. Replace [HOST-URL] with your W&B host URL:
```
wandb login --relogin --host=[HOST-URL]
export WANDB_BASE_URL=[HOST-URL]
```

After working through these checks, you can initialize and log a run to the target entity and project without permission errors.

Runs Security

Documentation Index