Executive summary. When a screen refuses you, read the refusal: it names which of the two is missing, and the two have completely different fixes.
Definition
A product is something the pharmacy buys. A permission is something your role holds. Either can stop you, and they are not the same problem.
What to do
Read the message itself rather than the fact that something was refused. It names what is missing, in the form "Supplier Catalogs is included in Attergo Platform".
If the message names a capability and a plan, your pharmacy does not hold that product. That is a purchasing decision and it goes to whoever owns the account, not to support.
If the message names a permission, your pharmacy holds the product and your role does not hold the right. That goes to your owner or administrator, who can change it on the Roles screen without buying anything.
Why the refusal is worded that way
A refusal that says only "forbidden" leaves you guessing between a missing licence, a missing product and a missing permission, and it leaves support guessing too. Naming the specific thing is the difference between a support conversation that ends in one message and one that takes three days.
The refusal comes from the server, not the screen. A screen that hid the button would leave you unable to tell the feature exists at all, and unable to ask for it.
Frequently asked questions
The screen is visible but everything on it is refused. Is it broken?
No. The screen exists so you can see what the capability is and decide whether you want it. What it cannot do is show you another pharmacy’s data or pretend to hold yours.
Referenced standards and further reading
- Attergo Knowledge Center ↗Attergo
Related articles
How to invite a colleague to your organization →