Apache Allura™

Forge software for hosting software projects

Brought to you by: alexluberg, brondsem, ccruz, deshani, and 11 others

#5517 Document permissions

Milestone: v1.0.0

Status: closed

Owner: Tim Van Steenburgh

Labels: sf-4 (350)

Component: General

Reviewer: Dave Brondsema

Updated: 2015-08-20

Created: 2012-12-26

Creator: Rich Bowen

Private: No

A project admin asks:

What does the "code Permissions" actually mean?

I assume "Write" is committing to the repository.
But...
...what's the difference between "Admin" and "Configure"?
...what is "Create" for?
...what are "Post", "Moderate" and "Unmoderated_Post" for? (sounds more
like forum stuff)

Would be great to have these permissions clearly documented, as to what exactly they do for each of the standard tools.

Related

Tickets: ~~#6300~~

Discussion

Dave Brondsema - 2013-01-02

[#1617] is pretty similar to this ticket.

Related

Tickets: ~~#1617~~

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2013-01-02

milestone: limbo --> forge-backlog
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2013-07-10

Milestone: forge-backlog --> forge-jul-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2013-07-15

Size: --> 4
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tim Van Steenburgh - 2013-07-15

status: open --> in-progress

assigned_to: Tim Van Steenburgh
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tim Van Steenburgh - 2013-07-18

status: in-progress --> code-review
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tim Van Steenburgh - 2013-07-18

forge:tv/5517
forge-classic:tv/5517

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2013-07-22

QA: Dave Brondsema
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2013-07-22

Looking great

Can we document the project-level permissions too? read/admin/create/update

"Repo read access." should note that direct (non-web) access to the repo is allowed.

Should we remove the "Not used" permissions?

Not really this ticket, but the crosshairs cursor on mouseover seems weird. Probably carryover from tools reordering.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2013-07-22

status: code-review --> in-progress
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2013-07-22

Some of our SF internal tools didn't get documented yet. One example is "view_private_lists"

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tim Van Steenburgh - 2013-07-23

forge:tv/5517
forge-classic:tv/5517

Deferring project-level perm descriptions and other permission cleanup to [#6084]. All the project-level perms except for 'read' appear to require 'admin' as well. Removing 'not used' permissions may require other code cleanup, and I didn't want to open that can of worms in this ticket. Also, we may want to keep some of those permissions after all, depending on what we do in [#6084].

Fixed repo 'read' description and cursor on perm cards.

Add descriptions for SF-specific apps.

Related

Tickets: #6084
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tim Van Steenburgh - 2013-07-23

status: in-progress --> code-review
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2013-07-23

status: code-review --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.