Project settings
A project's Settings tab gathers its name, its DSN, its domains, its keys and its emails. What you see depends on your role: members see the DSN and can mute its emails; admins and owners change the rest; only an owner can delete the project.
Name
How the project shows across the organization, up to 100 characters. Renaming it doesn't change its address: links keep working.
DSN
The value your applications need to report: set it as COLLECTOR_DSN in the applications that report to the project. It isn't secret. See Core concepts.
Rotate makes a new DSN with a new key. The current one keeps working for 24 hours, time to deploy the new one everywhere. Rotating is for when someone is sending events that shouldn't arrive, or when the DSN ended up somewhere it shouldn't be. It goes into the audit log.
A project created before DSNs could be shown again doesn't show it: rotate it to get one.
Domains
The web pages events came from, with their status. See Allowed domains.
Upload tokens and server keys
The project's two secrets: upload tokens, so your CI uploads source maps, and server keys, so your servers send logs. See Keys and tokens.
Muting the project
Emails: new and regressed issues are emailed to everyone in the organization. Turning Email me off mutes them just for you: the rest of the organization still gets them. Any member can mute a project. Alerts about servers that went quiet follow this setting too.
Deleting the project
Owners only. Its issues and events are deleted for good and its key stops working. To confirm, type the project's name. It can't be undone.
From the terminal
collector projects edit web-shop --name "Shop"
collector projects mute web-shop # unmute to get them again
collector dsn web-shop # only the DSN