---
title: "Storing secrets and parameters in the Configuration Store"
slug: "storing-secrets-and-parameters-in-the-configuration-store"
updated: 2024-09-26T13:11:38Z
published: 2024-09-26T13:11:38Z
canonical: "support.lusid.com/storing-secrets-and-parameters-in-the-configuration-store"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.lusid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Storing secrets and parameters in the Configuration Store

When you [create a job](/v1/docs/how-do-i-create-a-job), you have the option to pass in data at runtime in the form of command line arguments and/or environment variables.

For example, if the underlying Docker image exercises the LUSID SDK, you *must* pass in environment variables containing your SDK credentials. You *can* pass in other data, for example the [scope and code of a portfolio](/v1/docs/automatically-upserting-transactions-into-lusid-from-a-csv-file) to upload transactions to.

We recommend storing passwords, client secrets and tokens in the [Configuration Store](/v1/docs/configuration-store). Note that if you do not, **sensitive information may appear in the Scheduler logs**. You can optionally store non-sensitive parameters in the Configuration Store too, which may be more convenient if you pass the same data into multiple jobs. [See how to upload information to the Configuration Store](/v1/docs/how-do-i-upload-information-to-the-configuration-store).

Once uploaded, you can configure a job to pull information from the Configuration Store using an argument value such as `config://personal/00u91lo2eeX42sdse2p7/lusid-sdks/python-sdk/client-secret`. [See how to do this](/v1/docs/how-do-i-create-a-job).