8 artículos sobre Security, en orden de lectura.
Parsware Platform
Building an app doesn't give it to anyone. Share it with a role, check who that actually reaches, and the app appears on their launcher and nobody else's. The sharing travels in the solution, so you don't redo it in every environment.
Parsware Platform
Every table keeps four stamps for you, Created On, Created By, Modified On and Modified By, plus an Owner. Put them in a view or on a form and people see names and dates, not ids, with nothing to set up.
Parsware Platform
Every Parsware environment comes with an Organisation app. It holds your units as a chart, the people in each one, and who does which kind of work where, which is what processes route work by and what "my unit and below" access is measured against.
Parsware Platform
Every Parsware record has an owner, a person or a team, and the owner decides who can see it once access rules are set up. Hand a record on from its Owner field on the form, pick User or Team, and save.
Parsware Platform
A security role says what somebody may do with a table. A data policy says which records that reaches, and when a save is refused. We imported a sample with one of each kind, gave its role to two regional managers, and watched the same grant show each of them a different list and refuse one of them an approval.
Parsware Platform
A swimlane named Manager tells a reader who does the work. It tells the engine nothing until you give the lane a Role, picked from the environment's security roles. We set one on the leave-approval sample, added a lane, and followed a role from the designer to the people who hold it.
Parsware Platform
A user task has to land in somebody's list. It goes to whoever its Assigned to answers, or failing that whoever holds its lane's role in the run's unit, and a step can refuse the person who started the run. We went through each on the Leave Approval sample, and found the help page telling people to write something that doesn't work.
For Power Apps
Parsware for Power Apps runs inside your Dataverse environment. Your records are read in the browser as the signed-in user, and your designs are stored in Dataverse. The licence check makes no call. One request can leave, near a paid licence's expiry, and it carries the licence and nothing else. Here is what we measured.
