{style}
td.osp-spec-head {
  border-bottom: 1px solid #CCCCCC;
  padding-left: 0;
  padding-bottom: 1.0em;
}

td.osp-spec-head table.confluenceTable {
  display: table;
  margin: 0;
  padding: 0;
}

td.osp-spec-head th.confluenceTh, td.osp-spec-head table.confluenceTable th.confluenceTh {
  text-align: left;
  vertical-align: top;
  background-color: transparent;
  padding-left: 0;
  padding-right: 3em;
  border: 0;
}

td.osp-spec-head td.confluenceTd, td.osp-spec-head table.confluenceTable td.confluenceTd {
  border: 0;
}

.osp-spec h1, .osp-spec h2, .osp-spec h3, .osp-spec h4, .osp-spec h5, .osp-spec h6 {
  font-weight: bold;
  background-color: inherit;
  color: inherit;
  border: none;
  margin: 1.0em 0 0.2em;
  padding: 0;
}
.osp-spec h1 { font-size: 1.4em; }
.osp-spec h2 { font-size: 1.2em; }
.osp-spec h3 { font-size: 1.0em; }
.osp-spec h4 { font-size: 1.0em; font-style: italic; }
.osp-spec h5 { font-size: 0.9em; text-decoration: underline; }
.osp-spec h6 { font-size: 0.8em; font-style: italic; text-decoration: underline; }

.osp-spec table.confluenceTable {
  margin: 1.0em 2.0em;
}

.osp-spec p {
  margin: 0 0 0.5em 0;
}
{style}

{style:media=screen}
.osp-spec { width: 80em; margin: auto; border: 1px solid #CCCCCC; }
{style}

{style:media=print}
td.logocell, div.license, div.bottomshadow, div#poweredby, div.pageheader { display: none; }
div#PageContent table.pagecontent td.pagebody td.pagebody td.pagecontent > table { display: none; }
{style}

Specification ID:	OSP-SPEC-3
Working Title:	Change osp tool permission to use the sakai authz
Related Issue(s):	SAK-9782, SAK-10672, SAK-5979,
Component(s):	All osp components
Confirmation Status and Date:	Status: Confirmed Date: 8/20/2007

Summary

The OSP tools must use the sakai authorization structure.

Rationale

This will allow administrators to use the Realm tool to setup OSP tool permissions when setting other tool permissions.

Origin

Various institutions have complained about the in-ability to set OSP tool permissions at the same time as setting the other tool permissions.

Community Acceptance

This was briefly discussed at the OSP planning meeting for 2.5. Due to the level of agreement, no further discussions seemed necessary.

Behavior

All OSP tool permissions should be exposed in the Realms tool. Additionally, all OSP tool permissions may be settable in the tool itself (ie. a "Permissions" button). When permissions are set in the tool itself, they must be reflected in the Realms tool.

Conditions	Behavior
Set or unset an OSP Tool permission in the Realms tool for a site and role	Permission should be reflected in the tool on that site for that role
Set or unset and OSP tool permission in the OSP tool iteself	Permission should be reflected in the Realms tool for that site and role

Additionally, tools will not be displayed to users without appropriate permissions, as follows:

tool	required permission
Evaluations	evaluate
Forms	create
Portfolio Layouts	create
Portfolio Templates	create
Reports	view
Styles	create
matrix	create OR use OR review OR evaluate
Wizards	view OR review OR evaluate OR create

Interaction

Actors:

System Admin - The System Administrator is able to set OSP permissions from the Realms tool.

Quality Metrics

N/A

Assumptions

N/A

Outstanding Issues

N/A

Project: Portfolio

OSP-SPEC-3 - OSP Perms