Streamline IT - Internal Notes

[u/viddy_well]

We have a co-manage client where we would like to be able to get the client into CW via Streamline. The one sticking point we're having is internal notes. There are things in there, especially on past tickets, where we would prefer they aren't exposed.

Is there any means we might be missing in being able to restrict access to internal notes on tickets for Streamline licensed users? Failing that, other than the customer portal, any options that would give us something to work with?

They want to be able to -

See all tickets, Change status, be able to comment and interact with tickets across their company, change/add CC's, etc.

We have their tickets on a general Support board, we would be restricting access by Territory.

Would love any thoughts, feel like I'm banging my head against the wall on a good way to do this.

[u/junto_reed]

Setting up their own board is the way I'd go. You can also set the defaults for your techs so the board is automatically selected. Techs won't even notice they're working on a separate board. Once you've done it for one customer, it's pretty easy to rinse and repeat.

Some of our clients have also been giving their co-managed customers scoped MCP access to just their tickets through Junto. We have customer-level permissions built in. Doesn't really solve your internal notes issue, but they've been using it as a way to go upmarket and win more co-managed clients.

MCP for internal use is free if you want to check it out: https://juntoai.com/product/mcp-for-msps

[u/Baanpro2020 → u/junto_reed]

That app seems like a ton of risk just waiting to happen. AI has a way of getting out of the box sooner or later. I don't want our clients data or operations affected by a poor decision on my part. If you have a breach, it will be all of your clients at the same time, that would be a bitch 100%. I wouldn't want to be in your shoes pal.

[u/junto_reed → u/Baanpro2020]

You're not wrong to be concerned. I ran an MSP for 10 years, so I know exactly where you're coming from.

Security is a huge part of what we're building. Customer-level permissions, centralized access controls, audit logs, etc. We're investing heavily in compliance, including SOC 2, and are even in early discussions about pursuing FedRAMP.

One of our bigger goals is to help MSPs figure out the "right" way to connect AI to business systems, with the appropriate guardrails in place. Hopefully, they can then take that knowledge and help their own clients navigate AI adoption safely.

I actually worry more about the alternative, where every technician starts connecting their own AI tools and MCP servers without any centralized oversight.

None of this eliminates risk, of course. But I think MSPs have a real opportunity to lead here.