User Permissions

	A	B
1	Assumptions
2		FOLIO Apps provide base permissions for granular control over individual functions
3		These are grouped into "logical permissions" by app developers (e.g. logical permissions are defined in this document)
4		Logical permissons are often cumulative (e.g. can edit user will also confer can view user rights) so that we avoid predictable rights issues (e.g. user can edit but not view)
5		Logical permissions can be assigned directly to users
6		Logical permissions can be grouped into "permission sets" which can also be assigned to users
7		Permission sets can contain both logical permissons and other sets
8		Placeholder permissions should be prepended with "placeholder - "
9
10
11		When creating users like acq-admin and circ-admin - see: GitHub documentation: https://github.com/folio-org/folio-tools/tree/master/add-users
12		For example, given a file acq-admin.json that looks like
13		[
14		"Agreements: Delete agreements",
15		"Agreements: Edit agreements",
16		]
17		Create a user named "acq-admin" with the password "acq-admin", and create a permission-set named "acq-admin" that has those permissions. Assign that permission set, as well as all service points, to the user.
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100