This message was deleted.

I’m not sure there’s a good way to do that logistically, and regardless from a privacy perspective I don’t know that we should be discussing information another person provided to us with you even if we were somehow able to make that connection — after all, if they want you to know, they could share it with you themselves, and even CC you in their emails. That said, I definitely appreciate your perspective, and it’s something we’ll discuss. I think it’s important to keep in mind that in general when a person sends an email to another, the presumption is that a third party won’t have it shared with them without their express knowledge and consent, regardless of any personal or professional relationship that may exist. I think that’s an important “default”. #2 seems like a completely separate issue, and something we can delve into via support, since it will inherently require delving into the specific situation and app(s) involved. We haven’t had other reports like that though, if that provides some context.

I sent you a follow-up video. Perhaps our organization sets up support differently from others, but my team members are the only ones who can reach out to you. They handle tier 1 and tier 2 issues (records aren't loading, etc.). When something becomes tier 3 (i.e. Stacker says that it's a permissions issue, but we haven't made any changes to permissions and I need to follow up and figure out what happened on a development level), then it gets really tedious to gather all the details they've already submitted about the issue.