# Activating

The license connects the site to SleekWP's store; the standalone SleekByte
plugin uses it to receive updates. Snippets, the workspace and the CLI work
whether or not a license is active.

## On the License page

Open Byte's License page: in the suite it sits below Byte in the workspace
sidebar, and in the standalone plugin under `SleekWP > Byte`.

1. Enter the license key.
2. Choose **Activate license**.

The page asks the store to activate the key for this site and shows the
result as valid or invalid. Only a valid key is kept; an invalid one is
discarded. **Deactivate license** asks the store to release the key for this
site and removes it together with its status, after you confirm.

The page is hidden when the standalone plugin is
[white-labelled](/docs/white-label.md).

## With a constant

You can provide the key in PHP instead, for example in `wp-config.php`:

```php
define( 'SLEEK_BYTE_LICENSE', 'YOUR LICENSE KEY' );
```

While the constant holds a non-empty key, the License page shows that key,
masked, as managed by the constant, and refuses to activate or deactivate a
key entered on the page. The constant does not activate the key with the
store by itself.

## Uninstalling

Deleting the plugin removes Byte's settings, its license, its version markers,
its saved list of snippets, the previews with their temporary files in `uploads/sleek-byte-preview` and
their scheduled cleanup, and what the retired built-in AI chat and standalone
recovery editor left behind, on every site of a network. It keeps the snippets
in `uploads/sleek-byte`, which are the site's own code, with their error logs
and history, the local copies of external assets in
`uploads/sleek-byte-assets` and the plugins exported to
`uploads/sleek-byte-exports`. While another plugin that carries Byte is still
installed, such as the suite's Pro plugin after you delete the standalone
SleekByte plugin, Byte's data stays for it and deleting removes nothing.