Basestack Docs
User Guide

Settings & Configuration

Project settings allow you to configure your project, manage security, control access, and customize behavior. This comprehensive guide covers all settings available in your project.

Accessing Settings

To access project settings:

  1. Select your project from the Projects dropdown
  2. Click Settings in the navigation bar
  3. Choose a settings tab:
    • General - Project information and keys
    • Members - Team member management
    • Environments - Environment configuration
    • Security - Security and access controls

General Settings

The General settings tab contains essential project configuration.

Project Name

Update your project's display name:

  1. Click Edit next to Project Name
  2. Enter a new name (1-30 characters)
  3. Save changes

Changing the project name doesn't affect flags or API keys. It only updates the display name.

Project Owner

View project owner information:

  • Name - Owner's display name
  • Email - Owner's email address
  • Avatar - Owner's profile picture

The project owner has full control over the project. Only the owner can delete the project.

Endpoints

View API endpoints for integration:

  • Base URL - The base URL for API requests
  • Environment-specific endpoints - URLs for each environment

Use these endpoints when integrating with the REST API or configuring SDKs.

Project Key

View and copy your project key:

  1. Find the Project Key section
  2. Click to reveal the key
  3. Click Copy to copy to clipboard

Keep your project key secure. Never commit it to version control. Use environment variables in your applications.

Environment Keys

View and copy keys for each environment:

  1. Find the Keys section
  2. Select an environment
  3. Click to reveal the key
  4. Click Copy to copy to clipboard

Each environment has its own key. Use the appropriate key for each environment in your SDK configuration.

Delete Project

Permanently delete your project:

Deleting a project is permanent and cannot be undone. All flags, environments, member associations, and project data will be permanently removed.

To delete:

  1. Scroll to the Delete Project section
  2. Enter the project name to confirm
  3. Click Delete Project
  4. Confirm the deletion

Make sure you have backups of any important data before deleting a project. This action cannot be reversed.

Members Settings

Manage who has access to your project.

Viewing Members

The Members tab shows:

  • Member List - All project members
  • Member Details - Name, email, role, and avatar
  • Actions - Remove member option

Adding Members

Open Add Member Modal

Click Add Member button in the Members section.

Select from team members

Select a team member from the list of team members.

Assign project role

Assign a project role to the team member.

Managing Members

  • View Roles - See each member's current role
  • Change Roles - Update member permissions (if you have permission)
  • Remove Members - Remove members from the project

Only project owners and admins can manage members. Members can view the member list but cannot modify it.

Environments Settings

Configure and manage project environments.

Viewing Environments

The Environments tab shows:

  • Environment List - All environments in the project
  • Environment Details - Name and description
  • Actions - Create, edit, or delete options

Creating Environments

See the Environments guide for detailed instructions.

Managing Environments

  • Edit - Update environment name or description
  • Delete - Remove environments (removes all flag configs for that environment)

Deleting an environment will remove all flag configurations for that environment. Make sure you no longer need it before deleting.

Security Settings

Configure security and access controls for your project.

Allowed Websites

Restrict which websites can use your feature flags:

  1. Go to Settings → Security
  2. Find Allowed Websites section
  3. Enter domain names (one per line)
  4. Save changes

This helps prevent unauthorized use of your feature flags. Only requests from listed domains will be allowed.

Example:

example.com
www.example.com
app.example.com

Use this in production to ensure only your applications can access your flags. Leave empty for development.

IP Address Rules

Block specific IP addresses from accessing flags:

  1. Go to Settings → Security
  2. Find IP Rules section
  3. Enter IP addresses to block (one per line)
  4. Save changes

Blocked IPs will be unable to access any flags. Use this carefully and only when necessary.

Example:

192.168.1.100
10.0.0.50

Use IP blocking for security incidents or to prevent abuse. Consider using allowed websites instead for normal access control.

Best Practices

Key Management

  1. Never Commit Keys - Always use environment variables
  2. Separate by Environment - Use different keys for each environment
  3. Limit Access - Only share keys with authorized team members

Security Configuration

  1. Use Allowed Websites - Restrict access in production
  2. Monitor IP Rules - Review blocked IPs regularly
  3. Regular Audits - Review security settings periodically
  4. Document Changes - Keep records of security changes

Member Management

  1. Principle of Least Privilege - Give minimum necessary permissions
  2. Regular Reviews - Audit member access periodically
  3. Remove Promptly - Remove members who no longer need access
  4. Clear Roles - Assign appropriate roles from the start

Environment Management

  1. Standard Names - Use consistent environment names
  2. Don't Overcomplicate - Create only necessary environments
  3. Document Purpose - Describe what each environment is for
  4. Clean Up - Remove unused environments

Troubleshooting

Can't Access Settings

  • Verify you have permission to view settings
  • Check your project role (Developer, Tester, Viewer)
  • Ensure you're viewing the correct project
  • Contact project owner if needed

Keys Not Working

  • Verify you're using the correct key
  • Check that the key hasn't been rotated
  • Ensure you're using the right environment key
  • Review API endpoint configuration

Security Issues

  • Review allowed websites configuration
  • Check IP rules for blocked addresses
  • Verify environment keys are correct
  • Review member access and permissions

Member Issues

  • Verify member has been added to project
  • Check member's role and permissions
  • Ensure member has accepted invitation
  • Review project access settings

Next Steps

Now that you understand settings:

  1. Learn about feature flags →
  2. Set up environments →
  3. Integrate with SDKs →

Teams & Collaboration

Previous Page

Billing & Usage

Next Page

On this page

Accessing SettingsGeneral SettingsProject NameProject OwnerEndpointsProject KeyEnvironment KeysDelete ProjectMembers SettingsViewing MembersAdding MembersOpen Add Member ModalSelect from team membersAssign project roleManaging MembersEnvironments SettingsViewing EnvironmentsCreating EnvironmentsManaging EnvironmentsSecurity SettingsAllowed WebsitesIP Address RulesBest PracticesKey ManagementSecurity ConfigurationMember ManagementEnvironment ManagementTroubleshootingCan't Access SettingsKeys Not WorkingSecurity IssuesMember IssuesNext Steps