Hi Camille2,
That's definitely a bit of a head-scratcher, especially when everything looks like it should be working. Even if you've been invited in as an admin or file user, creating or managing report packs can sometimes be a bit picky with permissions. Usually this comes down to the level of access tied to the role in that file. A couple of things worth checking:
- Make sure the affected user has full admin access or has full access to that specific category and not set to read-only
- Double check they're logged in with the exact email address that was invited
If all that looks good and it's still chucking the error, it might be something we need to take a closer look at on our end. Best next step would be to jump onto our live chat support through our virtual assistant, MOCA, or submit a case via My Account so the team can dig into the file with you and sort it out properly.
Regards,
Sai