We are likely adding tool soon, however I just noticed we seem to have Loom blocked. I will request an update but that means a host of paperwork. So the question is basically will it ever be Atlassian to ensure access is available - especially if we're adding it as part of the TWC?
Hi Tere! Can you please share a screenshot of the error message you're seeing?
no error, we're re-directed to our co-pilot instance - which I think is odd but seems to be what IT configured. If I turn off Zscaler its allowed, but obviously - that's a no-no
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tere,
Just for my understanding is it only zscaler that is blocking access to Loom.
If that's the case it could mean that zscaler needs to create an exception rule and whitelist the Loom URL.
Best regards,
Bert Utrecht
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just adding FYI , please have a look at following post from loom support which describes requirements for loom to work within your network :
Domains, Protocols and Ports required for Loom to work on your servers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's definately our issue. I just need to get someone to add Loom to approved sights, I was just curious if there were plans to update to atlassian.loom for example which likely would have eliminated any IT concerns.
I can't get to the link above - support.loom (it's blocked lol) will review from home later.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for letting me know !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.