I know it asks to log in when accessing the global:fullPage URL, but it says I don’t have access, which might be because I’m trying to access it in a development environment with a user that’s not an admin. If it was in production would the globalFullPage module allow users to log in with an Atlassian account and access the module even if they are not licensed users in the cloud instance?
Hi @tayicknay,
Not by default. From the unlicensed-access page: “This is an optional property and its absence means that the module does not allow unlicensed users.”
A clean deploy won’t settle it either. I tried it on our lab app this morning with CLI 13.4.0: the validator accepted unlicensedAccess on global:fullPage, rejected it on jira:fullPage, then also accepted it on confluence:fullPage, which that same docs page says “does not support unlicensed or anonymous access”. Acceptance there follows the manifest schema and says nothing about rendering. I did not open the page as a real unlicensed user, so I can’t answer your production half.
What makes me doubt it: the global:ui page has an “Access and licensing” section saying “Unlicensed users cannot access the global:ui view”. Different module, but it’s the nearest thing Atlassian has published about a global surface and licensing.
Two things before you test. A non-admin who holds a product licence is still licensed, so they won’t exercise this. And the docs require distribution status Sharing before anyone unlicensed can reach the app. I think it’s the likelier cause of what you’re seeing, if your error is the “only the owner of this application may grant it access to their account” one.