# Performing administration tasks on the server side with a secret key

By default, server side rendering (SSR) does not permit the use of a `secret` key. This restriction is in place to prevent the accidental exposure of your `secret` key to the public. Since SSR runs on both the server and client side, it becomes challenging to separate the key specifically for client-side usage.

However, there is a solution. You can create a separate Supabase client using the `createClient` method from `@supabase/supabase-js` and provide it with the `secret` key. In a server environment, you also need to disable certain properties to ensure proper functionality. See the example code below for the required settings.

By implementing this approach, you can safely use the `secret` key without compromising security or exposing sensitive information to the public.

```ts
import { createClient } from '@supabase/supabase-js'

const supabase = createClient(supabaseUrl, secretKey, {
  auth: {
    persistSession: false,
    autoRefreshToken: false,
    detectSessionInUrl: false,
  },
})
```