Plugins:PluginDirectory/EditingWorkflow: Difference between revisions

Plugins:PluginDirectory/EditingWorkflow (view source)

Revision as of 00:20, 10 February 2010

5 bytes added , 10 February 2010

no edit summary

LesOrchard

Confirmed users

920

edits

@@ Line 13: / Line 13: @@
 ; guest : anonymous user, not logged in
 ; member : registered user, logged in
-; trusted : (''not yet implemented'') user assigned "editor" access to a subset of plugins by PFS ID (ie. a vendor, with access to manage their own plugins)
+; trusted : user assigned editor access to a subset of plugins by PFS ID (ie. a vendor, with access to manage their own plugins)
 ; editor : user with read/write/deploy access to plugin releases in all sandboxes
 ; admin : user with full read/write/delete access to both live and sandboxed plugin releases
@@ Line 56: / Line 56: @@
 == Editor approval ==
-Users with "editor" access have the ability to view/edit/delete data in any
+Users with editor access have the ability to view/edit/delete data in any
 user's sandbox.  From there, they can review sandboxed plugins, perform edits,
 and deploy a sandbox plugin live.
@@ Line 63: / Line 63: @@
 available to all users via the PFS search API.
-Users with "editor" access cannot create/edit/delete live plugins directly.
+Users with editor access cannot create/edit/delete live plugins directly.
 == Trusted users ==
-''This is not yet implemented.''
+Trusted users are assigned editor level access to specific plugins.  This is
+most useful for vendors, giving them self-service access to their own plugins.
-Trusted users are assigned "editor" level access to specific plugins.  This is
+Editors can add a user as trusted to a plugin from that user's sandbox.
-most useful for vendors, giving them self-service access to their own plugins.