[toekneestuck]

[I work at Jam]

- Yep, your header would be scrubbed by our default definition. And also: yes definitely, configurable scrubbing is on our radar/an inevitability. Sensible defaults has been our goal, but we're definitely aware that any given keyword may be sensitive to one company but not be to another! (e.g, an address in the context of a healthcare org's patients may be sensitive, but likely wouldn't be considered sensitive for an MLS search product)

- Re: Sentry — Makes sense! There's likely a lot of team-level configuration we can add for integrations over time

- Re: Linear — that's a good question. We used to have much deeper integration with some third parties, so I think we may be able to tighten up some of those scopes. I created a ticket for us to follow up on this, thank you!

[toekneestuck]

Quick follow up on the integration with Linear: just confirmed that we do not need write scopes on the workspace. The fix will be in production by next week :)

[sandstrom]

Great, thanks!

I made a mistake in my comments above:

I meant to write "Would be neat if the *Linear* integration had configurable fields (at the team level set which ones are visible, and set fixed values for some of them). For example, I don't want anyone to set the project (that's the triage step in Linear), and I want only some teams to be selectable, I'd like to skip the 'effort' altogether, etc."