person_update
Change what the company directory holds about one person: their name, their job title, their organization, who they report to, their phone number, the day they started, whether they administer the company, and whether they still work here. Only the fields the call names change. A person may correct their own phone number and start date; every other field, and anybody else's, is an administrator's. Ask the requester first before raising or lowering administrator rights or marking somebody departed; both are wide changes somebody has to mean. `workspace_write` · v2
Authorization
memberToken The tools internkim uses inside a company, callable from outside it. A token belongs to a person, and every call runs as that person, so a token can never do more than its owner can.
The first token is made signed in, from the settings screen. After that a token makes its own
successors: POST /token for a new one, DELETE /token for the old one, so a script rotates
without a browser. A token can neither mint a rung above its own nor revoke itself.
Send Authorization: Bearer <token> on every request.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
curl -X POST "https://example.com/tools/person_update/invoke" \ -H "Content-Type: application/json" \ -d '{ "input": { "personHint": "Sample Lee" } }'{ "toolName": "person_update", "outcome": "succeeded", "selectedBackend": "device", "effects": [ { "objectType": "person", "effect": "created", "id": "7a93de11-…" } ], "result": { "…": "the tool's own document" }}person_password_reset POST
Reset one person's password: their old password stops working and they get a temporary password to sign in with once. Only an administrator resets a password, and an administrator's password only its owner resets. The answer carries the temporary password, which is the only time it is readable, so pass it to the person who asked. Requires approval; the old password cannot be brought back. `destructive` · approval · v1
person_withdraw POST
Withdraw one person from the company: their membership ends, they can no longer sign in, they leave the company messenger, and every screen stops showing them, while the attendance, leave and tasks they left behind still read. Only an administrator withdraws people, and never themselves. With purge, the person is deleted outright instead when nothing refers to them. To delete what they wrote in the messenger, call person_message_delete first, while they are still in the directory. Requires approval; this action is irreversible. `destructive` · approval · v1