> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/api/client-libraries/redivis-python/reference/redivis/redivis.config.md).

# redivis.config

### **redivis.**<mark style="color:purple;">**config**</mark>**(\*, \[default\_workflow, default\_dataset, default\_user, default\_organization, api\_endpoint, config\_dir, tmp\_dir, max\_parallelization, progress])** → dict

Sets library-wide defaults, and returns the current configuration. Arguments that aren't passed are left as they are, and settings that haven't been set fall back to their [environment variables](https://docs.redivis.com/api/client-libraries/redivis-python/reference.md#environment-variables). Pass `None` to clear a previously set value.

Arguments passed directly to a method (e.g., `table.to_pandas_dataframe(progress=False)`) always take precedence over the configuration.

### **Parameters:**

**`default_workflow` :&#x20;*****str | Workflow | None***\
The workflow (`owner.workflow`) within which unqualified table, query, parameter, transform, notebook, and datasource references are resolved. In Redivis notebooks, this is set to the notebook's workflow.

**`default_dataset` :&#x20;*****str | Dataset | None***\
The dataset (`owner.dataset`) within which unqualified table and query references are resolved, when there's no default workflow.

**`default_user` :&#x20;*****str | User | None***\
The owner of unqualified dataset and workflow references.

**`default_organization` :&#x20;*****str | Organization | None***\
The owner of unqualified dataset and workflow references, when there's no default user.

**`api_endpoint` :&#x20;*****str | None***\
The base URL of the Redivis API. Defaults to `https://redivis.com/api/v1`.

**`config_dir` :&#x20;*****str | os.PathLike | None***\
The directory in which credentials are cached after logging in. Defaults to `~/.redivis`. Credentials for redivis.com are cached directly in this directory, and those for any other API endpoint in a subdirectory for its host (e.g., `environments/localhost_8080/`).

**`tmp_dir` :&#x20;*****str | os.PathLike | None***\
The directory in which to temporarily store data, such as for disk-backed data objects (e.g., [Table.to\_arrow\_dataset](https://docs.redivis.com/api/client-libraries/redivis-python/reference/table/table.to_arrow_dataset.md)). Defaults to the OS temp directory.

**`max_parallelization` :&#x20;*****int | None***\
The default for the `max_parallelization` argument of methods that read, download, or upload data in parallel, such as `table.to_pandas_dataframe()`, `table.download_files()`, and `table.add_files()`. When not set, each method uses its own default, based on the number of CPUs.

**`progress` :&#x20;*****bool | None***\
The default for the `progress` argument, which shows progress bars for long-running operations. Defaults to `True`.

### **Returns:**

**dict** — the current value of every setting, with `None` for those that aren't set.

### Examples

```python
redivis.config(default_workflow="jane.my_workflow", progress=False)

table = redivis.table("output_table")  # Within jane.my_workflow
df = table.to_pandas_dataframe()        # No progress bar

redivis.config()
# {'default_workflow': 'jane.my_workflow', 'default_dataset': None, ..., 'progress': False}

redivis.config(progress=None)  # Clear the setting, falling back to REDIVIS_PROGRESS
```


---

# 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://docs.redivis.com/api/client-libraries/redivis-python/reference/redivis/redivis.config.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.
