> For the complete documentation index, see [llms.txt](https://help.sesami.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sesami.co/zh-cn/guan-li/users.md).

# 用户

{% hint style="info" %}
注意：“用户”是 **不是** 与“资源”不同。资源是可预订/必需的实体（团队成员、房间、设备）。用户是可以登录管理工具的人。
{% endhint %}

## 管理门户：用户（访问、角色和权限）

本指南说明了您组织中的人员如何访问 Sesami 管理工具，以及在授予权限时需要考虑的事项。

### 常见用户角色

* **所有者 / 管理员** - 可全面访问所有功能和设置
* **地点经理** - 管理其所在地点的预订、资源和服务
* **团队成员 / 资源操作员** - 查看自己的日程，为客户办理签到，并管理自己的预订
* **前台 / POS 员工** - 查看和创建预订，有限的管理访问权限
* **只读** - 仅查看预订和日程

### 新增用户上手流程（清单）

{% stepper %}
{% step %}

#### 创建或确认 Shopify 员工账户

确保此人拥有 Shopify 员工账户（如有需要请创建一个）。
{% endstep %}

{% step %}

#### 分配正确的角色/权限

授予与其职责相匹配的适当角色或权限（所有者/管理员、经理、前台/POS、只读）。
{% endstep %}

{% step %}

#### 确认他们可以访问 Sesami 管理页面

验证用户可以登录并访问其所需的 Sesami 管理页面。
{% endstep %}
{% endstepper %}

<figure><img src="https://1798155128-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnDgiM1CWSLWRIbhORANO%2Fuploads%2FlnKnSS4ZOO3EASyKNt10%2FScreenshot%202026-06-19%20at%2011.58.21.png?alt=media&amp;token=05a52c59-afb3-4884-9f66-6fcbac548318" alt=""><figcaption></figcaption></figure>

#### 按套餐划分的用户限制

您可以创建的用户数量取决于您的订阅套餐：

| 套餐         | 用户上限      | 访问级别       |
| ---------- | --------- | ---------- |
| Small      | 1 个用户     | 商店：读写      |
| Pro        | 最多 5 个用户  | 商店：读写      |
| Premium    | 最多 10 个用户 | 商店：读写      |
| Enterprise | 自定义       | 高级管理门户访问控制 |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sesami.co/zh-cn/guan-li/users.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.