feature/fix-clippy-on-stable-channel
claude/smbcloud-github-app-k9641p
development
feature/apps
feature/build-release
feature/ci-docs
feature/ci-ruby-gems
feature/cicd
feature/completion
feature/dist-nuget
feature/fix-ci-sdk-pypi-rubygem
feature/fix-clippy-on-stable-channel
feature/fix-deployment-script
feature/github-email
feature/gresiq-v1
feature/project-new-structure
feature/rsync-deploy
feature/ruby-runner
feature/sdk-npm
feature/sdk-workflows
feature/smbcloud-cli-release-npm
feature/smbcloud-deploy
feature/wasm
main
release/v0.7.4
| 1 | # Auth |
| 2 | |
| 3 | Auth is the identity and account service. It handles signing users in and |
| 4 | managing their accounts, so you don't have to build that part yourself. |
| 5 | |
| 6 | ## What you can do |
| 7 | |
| 8 | - Sign users in and let them create accounts |
| 9 | - Manage sessions and accounts |
| 10 | - Run hosted auth apps for your end-user accounts |
| 11 | - Manage collaborators and shared access where it applies |
| 12 | |
| 13 | ## Two kinds of accounts |
| 14 | |
| 15 | Keep these separate as you read: |
| 16 | |
| 17 | - **Your smbCloud account** — how you sign in to the platform. |
| 18 | - **Auth app users** — the end users who sign in to *your* product through an |
| 19 | auth app you run on smbCloud. |
| 20 | |
| 21 | When a screen or guide talks about "users", check which of the two it means. |
| 22 | |
| 23 | ## Getting started |
| 24 | |
| 25 | 1. Create an auth app for your product. |
| 26 | 2. Wire your app to its sign-in and account flows. |
| 27 | 3. Manage users and access from the console. |
| 28 | |
| 29 | Building against Auth from code? The SDKs live in the |
| 30 | [Developer](/developer) section. |