Jump to conversation
Unresolved conversations (2)
@Convly Convly Mar 19, 2021
In fact, a condition can be applied to every permission. The **condition query object**, however, will only work for permission attached to a particular subject (aka entity). For instance, I could create a condition that allows me to access a particular page of the admin panel only if the server date is 5pm. In this scenario, my action is not related to any subject/entity and my condition would look like this: `handler: () => new Date().getHours() === 17`
Outdated
...setup-deployment-guides/configurations.md
pwizla
Pierre Wizla
@petersg83 petersg83 Mar 12, 2021
Just a thought, 21 seems USA centered to me. Can we find a more inclusive example? Also, the user is the admin user that doesn't have the `age` attribute. We don't allow this model to be customized in the `content-type-builder`. The attributes you can use seem to me to be: `firstname`, `lastname`, `username` and `email`.
Outdated
...setup-deployment-guides/configurations.md
pwizla derrickmehaffy
Pierre Wizla and DMehaffy
Resolved conversations (14)
@Convly Convly Mar 12, 2021
The handler can also be a condition object (same format as the object that can be returned from a handler function)
Outdated
...setup-deployment-guides/configurations.md
pwizla
Pierre Wizla
@petersg83 petersg83 Mar 12, 2021
To confirm with @Convly, I think this is a unique name. We may specigy this: the name behaves as an unique id
Outdated
...setup-deployment-guides/configurations.md
pwizla Convly
Pierre Wizla and Jean-Sébastien Herbaux
@petersg83 petersg83 Mar 12, 2021
shown ?
Outdated
...setup-deployment-guides/configurations.md
pwizla
Pierre Wizla
@petersg83 petersg83 Mar 12, 2021
The custom conditions are not really in addition of the 3 defaults roles, they are in addition of the roles in general I think. Is there another way of saying this?
Outdated
...setup-deployment-guides/configurations.md
pwizla
Pierre Wizla
@lauriejim lauriejim Mar 11, 2021
Adding, registering or declaring. These 3 words are used in this documentation. I think having just one would be enought and would add clarity on this point.
Outdated
...setup-deployment-guides/configurations.md
pwizla
Pierre Wizla
@lauriejim lauriejim Mar 11, 2021
`if your condition is based on a plugin` or `if your condition is declared into a plugin`? I think it's 2 completely different meanings.
Outdated
...setup-deployment-guides/configurations.md
petersg83 pwizla
Pierre Noël and Pierre Wizla
@lauriejim lauriejim Mar 11, 2021
Some notes for this section. 1. we used to add (string), (boolean), (function) when we do a list of properties like this. 2. same for (optional) for the `plugin` for exemple.
Outdated
...setup-deployment-guides/configurations.md
@lauriejim lauriejim Mar 11, 2021
```diff - `displayName`: the user name displayed in a friendly format, as showed in the admin panel + `displayName`: the name displayed in a friendly format, as showed in the admin panel ```
Outdated
...setup-deployment-guides/configurations.md
@derrickmehaffy derrickmehaffy Mar 10, 2021
We should expand on this stating that you construct the conditions but they can be applied dynamically at any time in any environment since the assignment of them is stored in the database, not the file system.
Outdated
...setup-deployment-guides/configurations.md
pwizla
Pierre Wizla
@derrickmehaffy derrickmehaffy Mar 10, 2021
Should we expand these example or is linking to sift enough?
Outdated
...setup-deployment-guides/configurations.md
pwizla
Pierre Wizla
@derrickmehaffy derrickmehaffy Mar 10, 2021
I'm wondering if we should put the Bronze, Silver, and Gold badges here as while it is assumed that if you have a higher tier license it would also work (unlikely we would ever release a feature that is only for bronze and not silver or gold). It may not be clear to the user. :thinking:
Outdated
...setup-deployment-guides/configurations.md
meganelacheny pwizla
meganelacheny and Pierre Wizla
@meganelacheny meganelacheny Mar 10, 2021
Avoid using "we": you should either replace with "the Strapi team" or rewrite the sentence differently.
Outdated
...setup-deployment-guides/configurations.md
derrickmehaffy
DMehaffy
@meganelacheny meganelacheny Mar 10, 2021
I would put that warning right after the title of that documentation.
...setup-deployment-guides/configurations.md
derrickmehaffy pwizla
DMehaffy and Pierre Wizla
@meganelacheny meganelacheny Mar 10, 2021
- Avoid using "easily" in a documentation! Not all users may find it easy 🙂 - Could be nice to add capital letters to the names of the default roles: Author, Editor, Super Admin. - Perhaps the "_This requires an EE license with a Bronze plan._" sentence could be improved. I think we should write "Enterprise Edition" instead of "EE" to make it clearer. It could also be better to explain that it's at least the Bronze plan that is required (but Silver & Gold also work).
Outdated
...setup-deployment-guides/configurations.md
derrickmehaffy
DMehaffy