McAfee EPOCDE-AA-BA Product Guide - Page 49

Working with permission sets, Creating a new permission set, User Management, Permission Sets, Actions

Page 49 highlights

Setting up permission sets Working with permission sets 6 Working with permission sets Permission sets can be created, deleted, modified, imported and exported as you can with many other objects in an ePolicy Orchestrator server. Tasks • Creating a new permission set on page 49 Providing access levels between seeing everything or nothing requires you to create a permission set. • Modifying an existing permission set on page 50 The permissions granted within a specific permission set can be modified at any time. • Duplicating a permission set on page 50 Occasionally, the easiest way to create a new permission set is to duplicate an existing one similar to what you want. • Exporting permission sets on page 50 Once you have fully defined your permission sets, the fastest way to migrate them to other ePolicy Orchestrator servers is to export them and import them onto other servers. • Importing permission sets on page 51 Permission sets can take some time to configure, so exporting and importing them is a quick way to move this configuration from one ePolicy Orchestrator server to another. • Removing a permission set on page 51 Permission sets can be deleted when they are no longer required. • Deleting permission sets on page 51 Use this task to delete a permission set. Only global administrators can delete permission sets. Creating a new permission set Providing access levels between seeing everything or nothing requires you to create a permission set. If you want to create a new permission set that is unlike other permission sets you have created to this point, starting with this task is the best approach. If you want a new permission set that is similar to another existing permission set, it is easier to duplicate that permission set and modify the duplicate. Task For option definitions, click ? in the interface. 1 Open the permission sets page by clicking Menu | User Management | Permission Sets. 2 Click Actions | New. 3 Enter a name for the new permission set. ePolicy Orchestrator will not allow you to use a name that already exists. Each permission set name must be unique. 4 If you want to immediately assign specific users to this permission set, select their user names in the Users section. 5 If there are any Active Directory groups where you want all users from that group mapped to this permission set, select the server from the Server Name drop-down list and click Add. 6 If you have added any Active Directory servers you want to remove, select them in the Active Directory list box click Remove. 7 Click Save to create the permission set. At this point, you have created the permission set but have not yet assigned permissions to it. McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide 49

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 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
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328

Working with permission sets
Permission sets can be created, deleted, modified, imported and exported as you can with many other
objects in an ePolicy Orchestrator server.
Tasks
Creating a new permission set
on page 49
Providing access levels between seeing everything or nothing requires you to create a
permission set.
Modifying an existing permission set
on page 50
The permissions granted within a specific permission set can be modified at any time.
Duplicating a permission set
on page 50
Occasionally, the easiest way to create a new permission set is to duplicate an existing one
similar to what you want.
Exporting permission sets
on page 50
Once you have fully defined your permission sets, the fastest way to migrate them to other
ePolicy Orchestrator servers is to export them and import them onto other servers.
Importing permission sets
on page 51
Permission sets can take some time to configure, so exporting and importing them is a
quick way to move this configuration from one ePolicy Orchestrator server to another.
Removing a permission set
on page 51
Permission sets can be deleted when they are no longer required.
Deleting permission sets
on page 51
Use this task to delete a permission set. Only global administrators can delete permission
sets.
Creating a new permission set
Providing access levels between seeing everything or nothing requires you to create a permission set.
If you want to create a new permission set that is unlike other permission sets you have created to
this point, starting with this task is the best approach. If you want a new permission set that is similar
to another existing permission set, it is easier to duplicate that permission set and modify the duplicate.
Task
For option definitions, click
?
in the interface.
1
Open the permission sets page by clicking
Menu
|
User Management
|
Permission Sets
.
2
Click
Actions
|
New
.
3
Enter a name for the new permission set.
ePolicy Orchestrator will not allow you to use a name that already exists. Each permission set name
must be unique.
4
If you want to immediately assign specific users to this permission set, select their user names in
the
Users
section.
5
If there are any Active Directory groups where you want all users from that group mapped to this
permission set, select the server from the
Server Name
drop-down list and click
Add
.
6
If you have added any Active Directory servers you want to remove, select them in the Active
Directory list box click
Remove
.
7
Click
Save
to create the permission set.
At this point, you have created the permission set but have not yet assigned permissions to it.
Setting up permission sets
Working with permission sets
6
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide
49