> ## Documentation Index
> Fetch the complete documentation index at: https://plivo.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Configuring credentials
> Store Plivo auth credentials securely in GitHub Secrets
You also need to know your Plivo Auth ID and Auth Token, which you can find on the overview screen of the [Plivo console](https://cx.plivo.com/home).
But you don’t want to put your authentication credentials or other private information into your YAML file. If you’re working in a public repository, the YAML file is exposed to everyone, so your secrets would be exposed too.
Fortunately, [GitHub](https://docs.github.com/en/actions/reference/encrypted-secrets) has a way to keep this information secret. Go to your repository’s settings and select Secrets from the left menu bar.
Add the secrets related to your project in this section. Once you’ve put them up, you won’t be able to read them in the UI. Instead, you access them through notation like `${{secrets.SECRET_NAME}}`.
Create these secrets for this workflow:
* `PLIVO_AUTH_ID` : A Plivo Auth ID which can be found in [console](https://cx.plivo.com/home)
* `PLIVO_AUTH_TOKEN` : A Plivo Auth Token which can be found in [console](https://cx.plivo.com/home)
* `FROM_NUMBER` : Phone number in your Plivo account to send the SMS from.
* `TO_NUMBER` : Phone number to send the SMS to
**Note**: Secret names are case-sensitive.