{"_id":"5b0e13ffc4664e0003c75c98","version":{"_id":"5b0e13ffc4664e0003c75a67","project":"5b0e13ffc4664e0003c75a66","__v":4,"createdAt":"2015-09-17T16:58:03.490Z","releaseDate":"2015-09-17T16:58:03.490Z","categories":["5b0e13ffc4664e0003c75a68","5b0e13ffc4664e0003c75a69","5b0e13ffc4664e0003c75a6a","5b0e13ffc4664e0003c75a6b","5b0e13ffc4664e0003c75a6c","5b0e13ffc4664e0003c75a6d","5b0e13ffc4664e0003c75a6e","5b0e13ffc4664e0003c75a6f","5b0e13ffc4664e0003c75a70","5b0e13ffc4664e0003c75a71","5b0e13ffc4664e0003c75a72","5b0e13ffc4664e0003c75a73","5b0e13ffc4664e0003c75a74","5b0e13ffc4664e0003c75a75","5b0e13ffc4664e0003c75a76","5b0e13ffc4664e0003c75a77","5b0e13ffc4664e0003c75a89","5b0e13ffc4664e0003c75a8a","5b0e13ffc4664e0003c75a9d","5b0e13ffc4664e0003c75a9e","5b0e13ffc4664e0003c75a9f","5b0e13ffc4664e0003c75aa0","5b0e13ffc4664e0003c75aa1","5b0e13ffc4664e0003c75aa2","5b0e13ffc4664e0003c75aa3","5b0e13ffc4664e0003c75aa4","5b0e13ffc4664e0003c75aa5","5b0e13ffc4664e0003c75aa6","5b0e13ffc4664e0003c75aa7","5b0e13ffc4664e0003c75aa8","5b0e13ffc4664e0003c75aa9","5b0e13ffc4664e0003c75aaa","5b0e13ffc4664e0003c75aab","5b0e13ffc4664e0003c75aac","5b0e13ffc4664e0003c75aad","5b0e13ffc4664e0003c75aae","5b0e13ffc4664e0003c75aaf","5b0e13ffc4664e0003c75ab2","5bb3374f4306ad0003eb18e7","5bbf3c5373e72a000318362b","5bc065567d1cb0000384c649","5cbf19a5f9181f0033fbb968"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"__v":0,"category":{"_id":"5b0e13ffc4664e0003c75a75","project":"5b0e13ffc4664e0003c75a66","version":"5b0e13ffc4664e0003c75a67","__v":0,"sync":{"url":"","isSync":false},"reference":true,"createdAt":"2015-09-17T17:34:34.937Z","from_sync":false,"order":32,"slug":"api","title":"API Reference"},"parentDoc":null,"user":"554340dfb7f4540d00fcef1d","project":"5b0e13ffc4664e0003c75a66","githubsync":"","metadata":{"title":"","description":"","image":[]},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-10-29T21:17:26.225Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"examples":{"codes":[]},"method":"put","results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":true,"order":25,"body":"This call changes a project member's permissions for a specified project.\n\nUsers may have the following permissions on the Platform:\n  * Read\n  * Write\n  * Copy\n  * Execute\n  * Admin\n\nFor more information, see the documentation on [setting project member permissions](doc:set-permissions). Note that some user permissions imply others: for example, if you give a user admin permission, then they automatically receive read, write, copy and execute permissions.\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"PUT and PATCH\",\n  \"body\": \"The DataSTAGE powered by Seven Bridges API has two method to modify project members' permissions. This method uses the HTTP verb `PUT`, and the other uses the HTTP verb `PATCH`. \\n\\nThe difference between the two concerns the way that they update the information stored about the user. `PATCH` allows you to update just one part of the user's information -- for instance, just the value stored for the user's `copy` permission. On the other hand, a `PUT` request will fully overwrite the user's permission information. This means that when issuing a `PUT` request you must enter values for every key required to describe the user, even if the values for some keys are unchanged.\"\n}\n[/block]\n\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"https://f4c-api.sbgenomics.com/v2/projects/{project_owner}/{project}/members/{username}/permissions\",\n      \"language\": \"text\",\n      \"name\": \"Path\"\n    }\n  ]\n}\n[/block]\n##Request\n\n###Example request\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"PUT /v2/projects/rfranklin/my-project/members/crick/permissions HTTP/1.1\\nHost: f4c-api.sbgenomics.com\\nX-SBG-Auth-Token: 3259c50e1ac5426ea8f1273259740f74\\n\",\n      \"language\": \"http\",\n      \"name\": null\n    },\n    {\n      \"code\": \"curl -X PUT --data-binary \\\":::at:::permissions-for-crick.json\\\" -H \\\"X-SBG-Auth-Token: ce7ae5ab85e946599298e88a3430fba0\\\" 'http://f4c-api.sbgenomics.com/v2/projects/rfranklin/my-project/members/crick/permissions'\",\n      \"language\": \"curl\",\n      \"name\": \"cURL\"\n    }\n  ],\n  \"sidebar\": true\n}\n[/block]\n###Header Fields\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"`X-SBG-Auth-Token`\\n<span style=\\\"color:red\\\"><i>required</i></span>\",\n    \"0-1\": \"Your Platform [authentication token](doc:get-your-authentication-token).\",\n    \"h-2\": \"\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]\n###Path parameters\n[block:parameters]\n{\n  \"data\": {\n    \"0-0\": \"`project`\",\n    \"1-0\": \"`project_owner`\",\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-1\": \"The short name of the project containing the project member.\",\n    \"1-1\": \"The owner of the project containing the project member.\",\n    \"2-0\": \"`username`\",\n    \"2-1\": \"The Platform username of the user whose permissions you are overwriting.\"\n  },\n  \"cols\": 2,\n  \"rows\": 3\n}\n[/block]\n###Query parameters\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Data type\",\n    \"h-2\": \"Description\",\n    \"0-0\": \"`fields`\",\n    \"0-1\": \"string\",\n    \"0-2\": \"Selector specifying a subset of fields to include in the response.\"\n  },\n  \"cols\": 3,\n  \"rows\": 1\n}\n[/block]\n##Request body\nIn the body, you should enter a list of key-value pairs. The keys, and the values they take, are described in the following table.\n[block:parameters]\n{\n  \"data\": {\n    \"0-0\": \"`read`\",\n    \"0-1\": \"Boolean: `true` or `false`\",\n    \"0-2\": \"User can view file names, metadata, and workflows. They cannot view file contents.\\n\\nAll members of a project have `read` permissions by default. Even if you try setting `read` permissions to `false`, they will still default to `true`.\",\n    \"1-0\": \"`write`\",\n    \"1-1\": \"Boolean: `true` or `false`\",\n    \"1-2\": \"User can add, modify, and remove files and workflows in a project.\\n\\nSet value to `true` to assign the user copy permission. Set to `false` to remove copy permission..\",\n    \"h-0\": \"Key\",\n    \"h-1\": \"Data type of value\",\n    \"h-2\": \"Description of value\",\n    \"2-0\": \"`copy`\",\n    \"2-1\": \"Boolean: `true` or `false`\",\n    \"2-2\": \"User can view file content, copy, and download files from a project.\\n\\nSet value to `true` to assign the user copy permission. Set to `false` to remove copy permission.\",\n    \"3-0\": \"`execute`\",\n    \"4-0\": \"`admin`\",\n    \"3-1\": \"Boolean: `true` or `false`\",\n    \"4-1\": \"Boolean: `true` or `false`\",\n    \"3-2\": \"User can execute workflows and abort tasks in a project.\\n\\nSet value to `true` to assign the user copy permission. Set to `false` to remove copy permission.\",\n    \"4-2\": \"User can modify another user's permissions on a project, add or remove people from the project and manage funding sources. They also have all of the above permissions.\\n\\nSet value to `true` to assign the user copy permission. Set to `false` to remove copy permission.\"\n  },\n  \"cols\": 3,\n  \"rows\": 5\n}\n[/block]\n###Example request body\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"{\\n  \\\"read\\\": true,\\n  \\\"write\\\": true,\\n  \\\"copy\\\": true,\\n  \\\"execute\\\": true,\\n  \\\"admin\\\": false\\n}\",\n      \"language\": \"json\"\n    }\n  ],\n  \"sidebar\": true\n}\n[/block]\n##Response\n\n[See a list of response codes that may be contained in the body of the response.](doc:api-status-codes)\n\n###Example response body \n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"{\\n  \\\"write\\\": true,\\n  \\\"read\\\": true,\\n  \\\"copy\\\": true,\\n  \\\"execute\\\": true,\\n  \\\"admin\\\": false\\n}\",\n      \"language\": \"json\"\n    }\n  ]\n}\n[/block]","excerpt":"/projects/{project_owner}/{project}/members/{username}/permissions","slug":"set-a-project-members-privileges","type":"endpoint","title":"Overwrite a project member's permissions"}

putOverwrite a project member's permissions

/projects/{project_owner}/{project}/members/{username}/permissions

This call changes a project member's permissions for a specified project. Users may have the following permissions on the Platform: * Read * Write * Copy * Execute * Admin For more information, see the documentation on [setting project member permissions](doc:set-permissions). Note that some user permissions imply others: for example, if you give a user admin permission, then they automatically receive read, write, copy and execute permissions. [block:callout] { "type": "success", "title": "PUT and PATCH", "body": "The DataSTAGE powered by Seven Bridges API has two method to modify project members' permissions. This method uses the HTTP verb `PUT`, and the other uses the HTTP verb `PATCH`. \n\nThe difference between the two concerns the way that they update the information stored about the user. `PATCH` allows you to update just one part of the user's information -- for instance, just the value stored for the user's `copy` permission. On the other hand, a `PUT` request will fully overwrite the user's permission information. This means that when issuing a `PUT` request you must enter values for every key required to describe the user, even if the values for some keys are unchanged." } [/block] [block:code] { "codes": [ { "code": "https://f4c-api.sbgenomics.com/v2/projects/{project_owner}/{project}/members/{username}/permissions", "language": "text", "name": "Path" } ] } [/block] ##Request ###Example request [block:code] { "codes": [ { "code": "PUT /v2/projects/rfranklin/my-project/members/crick/permissions HTTP/1.1\nHost: f4c-api.sbgenomics.com\nX-SBG-Auth-Token: 3259c50e1ac5426ea8f1273259740f74\n", "language": "http", "name": null }, { "code": "curl -X PUT --data-binary \"@permissions-for-crick.json\" -H \"X-SBG-Auth-Token: ce7ae5ab85e946599298e88a3430fba0\" 'http://f4c-api.sbgenomics.com/v2/projects/rfranklin/my-project/members/crick/permissions'", "language": "curl", "name": "cURL" } ], "sidebar": true } [/block] ###Header Fields [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "`X-SBG-Auth-Token`\n<span style=\"color:red\"><i>required</i></span>", "0-1": "Your Platform [authentication token](doc:get-your-authentication-token).", "h-2": "" }, "cols": 2, "rows": 1 } [/block] ###Path parameters [block:parameters] { "data": { "0-0": "`project`", "1-0": "`project_owner`", "h-0": "Name", "h-1": "Description", "0-1": "The short name of the project containing the project member.", "1-1": "The owner of the project containing the project member.", "2-0": "`username`", "2-1": "The Platform username of the user whose permissions you are overwriting." }, "cols": 2, "rows": 3 } [/block] ###Query parameters [block:parameters] { "data": { "h-0": "Name", "h-1": "Data type", "h-2": "Description", "0-0": "`fields`", "0-1": "string", "0-2": "Selector specifying a subset of fields to include in the response." }, "cols": 3, "rows": 1 } [/block] ##Request body In the body, you should enter a list of key-value pairs. The keys, and the values they take, are described in the following table. [block:parameters] { "data": { "0-0": "`read`", "0-1": "Boolean: `true` or `false`", "0-2": "User can view file names, metadata, and workflows. They cannot view file contents.\n\nAll members of a project have `read` permissions by default. Even if you try setting `read` permissions to `false`, they will still default to `true`.", "1-0": "`write`", "1-1": "Boolean: `true` or `false`", "1-2": "User can add, modify, and remove files and workflows in a project.\n\nSet value to `true` to assign the user copy permission. Set to `false` to remove copy permission..", "h-0": "Key", "h-1": "Data type of value", "h-2": "Description of value", "2-0": "`copy`", "2-1": "Boolean: `true` or `false`", "2-2": "User can view file content, copy, and download files from a project.\n\nSet value to `true` to assign the user copy permission. Set to `false` to remove copy permission.", "3-0": "`execute`", "4-0": "`admin`", "3-1": "Boolean: `true` or `false`", "4-1": "Boolean: `true` or `false`", "3-2": "User can execute workflows and abort tasks in a project.\n\nSet value to `true` to assign the user copy permission. Set to `false` to remove copy permission.", "4-2": "User can modify another user's permissions on a project, add or remove people from the project and manage funding sources. They also have all of the above permissions.\n\nSet value to `true` to assign the user copy permission. Set to `false` to remove copy permission." }, "cols": 3, "rows": 5 } [/block] ###Example request body [block:code] { "codes": [ { "code": "{\n \"read\": true,\n \"write\": true,\n \"copy\": true,\n \"execute\": true,\n \"admin\": false\n}", "language": "json" } ], "sidebar": true } [/block] ##Response [See a list of response codes that may be contained in the body of the response.](doc:api-status-codes) ###Example response body [block:code] { "codes": [ { "code": "{\n \"write\": true,\n \"read\": true,\n \"copy\": true,\n \"execute\": true,\n \"admin\": false\n}", "language": "json" } ] } [/block]