Changes between Version 18 and Version 19 of SPIDocs


Ignore:
Timestamp:
Sep 22, 2014 8:57:51 AM (8 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SPIDocs

    v18 v19  
    332332When a user with the `ADD_USER` permission wants to invite another user to join the project, the inviting user calls the `addUsers` operation with the projectid, a list of users, proposed permissions, and an a URL prefix that serves the same purpose as the prefix on `joinProject`.  When the operation succeeds, each invited user receives a [wiki:SPIDocs#Notifications notification] containing a challenge (and descriptive text about the project).  If the invited user does wish to join, they call the `addUserConfirm` operation with the challenge.  When that operation succeeds, they are a member of the project.
    333333
     334A user with the `REMOVE_USER` permission can unilaterally remove other users from the project by calling the `removeUsers` operation.  The owner of a project cannot be so removed.
     335
     336==== Ownership ====
     337
     338When a project is created, an owner for that project is designated.  It is generally the user who successfully called `createProject`, though ownership may be designated for projects created by administrators.  The owner's identity may be a factor in project approval, depending on how the testbed is administered.
     339
     340The owner is given all permissions to a project and these generally cannot be altered.  The owner of a project cannot be removed from the project.
     341
     342The owner (and administrators) can change the owner of a project by calling the `setOwner` operation.
     343
    334344==== Changing Permissions ====
    335345
    336 A user that has both `ADD_USER` and `REMOVE_USER` permissions to a group can change the permissions granted to a user in the group.  The `changePermissions` operation in the `Projects` service is used to do this.  It takes a projectid, a list of users, and a new set of permissions.  It returns an array of results indicating the outcome of each projected change.
     346A user that has both `ADD_USER` and `REMOVE_USER` permissions to a group can change the permissions granted to a user in the group.  The `changePermissions` operation in the `Projects` service is used to do this.  It takes a projectid, a list of users, and a new set of permissions.  It returns an array of results indicating the outcome of each requested change.
     347
     348==== Profile Management ====
     349
     350The `Projects` [wiki:SPIDocs#Services service] supports the operations described in the [wiki:SPIDocs#Profiles profiles] description to allow applications to manipulate project profiles.
     351
     352==== Administrative Operations ====
     353
     354There are a few more operations that are restricted to administrators.
     355
     356There are [wiki:SPIDocs#Profiles profile] operations to add, remove and change attributes to the project profile schema.
     357
     358There is an operation, `addUsersNoConfirm` to add users to a project without requiring the users being added to confirm the change.
     359
     360These are documented below.