This method provides detailed information for a scope:
...
if and how a user can access segments in the given scope . A scope can be a job, project, global search, a translation memory and so on.
Gives full answers to:
- Can the user access segments in the scope or notAccessible in the first place? For example, a translator most often cannot access the segments in a project.
- What are the accessible languages, segment fields, custom fields, labels, etc.?
- Allowed Which editing operations such as for are allowed? Can I edit texts, meta information, split/merge etc.Lists all ?
- What are the languages with code and name, all custom fields, all labels custom field codes and names and so on?
This information can be used if you build a translation editing interface and you need to know in advance what information the user can access and modify.
...
(POST) /api/resources/segments/rights
PARAMETERS
The message body contains a JSON object:
BODY | The scope json object. For example, for a job, project, memory, term base, global search etc. Example for a job:
Example for a project:
See Scope (Object) for more details. | object, Mandatory |
...