DoCreate
Sign Up

Projects

Create and manage projects in DoCreate

Projects are the primary organizational unit in DoCreate. They allow you to group related templates and API keys together, making it easy to manage access and track usage across different applications or environments.

What Is a Project?

A project represents a distinct application, service, or environment that uses DoCreate for PDF generation. For example, you might create separate projects for:

  • Production and Staging environments of the same application.
  • Different products or services within your organization.
  • Client projects if you are an agency managing multiple customers.

Each project has its own set of API keys and usage tracking. This isolation ensures that one project cannot access another project's resources.

Creating a Project

  1. Navigate to your team dashboard.
  2. Click New Project.
  3. Enter a name for the project (e.g., "Production", "Invoice Service", "Client Portal").
  4. Optionally add a description to help team members understand the project's purpose.
  5. Click Create.

Your project is now ready. The next step is to create an API key for the project so you can start making API requests.

Managing Projects

Viewing Projects

All projects in your team account are listed on the dashboard. Each project card shows:

  • The project name and description.
  • The number of active API keys.
  • Recent usage statistics.

Editing a Project

To update a project's name or description:

  1. Click on the project to open its detail page.
  2. Navigate to Settings.
  3. Update the fields you want to change.
  4. Click Save.

Deleting a Project

Deleting a project permanently removes it along with all associated API keys. This action cannot be undone.

  1. Open the project's Settings page.
  2. Scroll to the Danger Zone section.
  3. Click Delete Project.
  4. Confirm the deletion by typing the project name.

All API keys associated with the deleted project will immediately stop working. Make sure to update any applications that reference those keys before deleting the project.

Best Practices

  • Use separate projects for each environment. Create distinct projects for development, staging, and production. This prevents accidental use of production keys in non-production environments.
  • Name projects clearly. Use descriptive names that make it obvious what each project is for, especially in team accounts with multiple members.
  • Review projects regularly. Remove projects that are no longer in use to keep your account organized and reduce the risk of unused API keys being compromised.