Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Public URL's / Custom URL's for Calendar sharing

Avatar

Level 5

I want to share a calendar enterprise-wide without requiring employees to login via SSO, which could create thousands of requestors.

I know that I can create a public URL, but then, I have a public URL ... that's a security/confidentiality risk. What I really want is a "public to Enterprise" link.

Is there a preference that would let me specify the base URL, so that it's a URL that exists behind our firewall?

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Reply

Avatar

Level 10

Interesting challenge Howard,

We recently invented something similar as part of our Magic Reports solution. One of our clients wanted a such a "public to Enterprise" link to a portfolio specific version of our Hotsheet solution in order to then post that link under its corresponding Portfolio channel within MS Teams so the (non-Workfront) users within Teams could then simply "see" the report without having to log in to Workfront (not to mention set all of them up with requestor licenses...same deal as you).

To solve it, we set up an API Key under a special Workfront User, then at the Workfront Portfoio level, created a calculated custom parameter that combined the Portfolio ID with that API Key into a single URL that then opened Hotsheet for "THAT Portfolio, as THAT User", and -- presto! -- after then pasting those links into MS Teams, all Teams Users could see what they needed, pulling in real time from Workfront, without having to resort to using the ("too loose") Public URL.

So, although in your case you're not using one of our Magic Reports (although I'd be happy to chat further on that front via doug.denhoed@atappstore.com if you'r interested), perhaps by describing the technique we invented you can adapt it to use the built in Workfront Reports you're attempting to expose -- whether you then use MS Teams to house it, or just send the URL out "raw" to those who need it.

I'm interested to hear how it goes!

Regards,

Doug