Create Application
Applications in Docstron help you organize and manage your PDF generation workflow. Each application acts as a separate workspace where you can create templates, generate documents, and track usage.
Why Use Applications?
Section titled “Why Use Applications?”Applications provide several benefits:
- 🗂️ Organization - Separate projects, clients, or environments
- 🔐 Isolation - Keep templates and documents organized per application
- 📊 Usage Tracking - Monitor API usage and document generation per application
- 🎯 Easy Management - Quickly switch between different projects
- 🏢 Multi-tenant Support - Perfect for agencies managing multiple clients
Common Use Cases
Section titled “Common Use Cases”- Separate by Project - Different application for each product or service
- Environment Separation - Development, staging, and production applications
- Client Management - One application per client for agencies
- Department Separation - Different applications for sales, HR, accounting, etc.
Creating Your First Application
Section titled “Creating Your First Application”Follow these simple steps to create an application via the dashboard:
Step 1: Access Applications Dashboard
Section titled “Step 1: Access Applications Dashboard”- Log in to your Docstron Dashboard
- Navigate to the Applications section from the sidebar
Step 2: Click Create Application
Section titled “Step 2: Click Create Application”Once you’re on the Applications page:
- Look for the “Create Application” button (usually at the top-right)
- Click on it to open the application creation form
Step 3: Fill in Application Details
Section titled “Step 3: Fill in Application Details”You’ll see a form with the following fields:
Application Name (Required)
Section titled “Application Name (Required)”Enter a descriptive name for your application. This helps you identify the purpose of the application.
Examples:
Invoice Generator
E-commerce Reports
Customer Certificates
Production Environment
Client ABC - Invoicing
Tips for naming:
- Use clear, descriptive names
- Include the project or client name
- Mention the environment if applicable (dev, staging, prod)
- Keep it concise but meaningful
Description (Optional)
Section titled “Description (Optional)”Add a brief description to provide more context about the application’s purpose.
Examples:
"Generates invoices for our e-commerce platform"
"Monthly sales reports and analytics documents"
"Production environment for client invoicing system"
"Development testing for new template features"
Status (Required)
Section titled “Status (Required)”Select the status for your application:
- Active - The application is enabled and can be used for template creation and document generation
- Inactive - The application is disabled and cannot generate documents (useful for temporarily disabling an application)
When to use each status:
- Choose Active for applications you’re currently using
- Choose Inactive for applications you want to pause or disable temporarily without deleting them
💡 Tip: You can change the application status later from the application settings if needed.
Step 4: Create the Application
Section titled “Step 4: Create the Application”- Review your application name and description
- Click the “Create Application” button
- Your application will be created instantly!
Step 5: Application Created Successfully
Section titled “Step 5: Application Created Successfully”After creation, you’ll:
- See your new application in the applications list
- Get a unique Application ID (e.g.,
app_abc123xyz
) - Be able to start creating templates within this application
Best Practices
Section titled “Best Practices”✅ Do’s
Section titled “✅ Do’s”- Create separate applications for different projects or environments
- Use descriptive names that clearly indicate the application’s purpose
- Add descriptions to provide context for team members
- Organize by client if you’re managing multiple clients
- Keep production separate from development/testing applications
❌ Don’ts
Section titled “❌ Don’ts”- Don’t create too many unnecessary applications - keep it organized
- Don’t use vague names like “App1” or “Test” for production applications
- Don’t mix unrelated projects in the same application
- Don’t forget to document the purpose of each application
Application ID
Section titled “Application ID”Each application receives a unique identifier called an Application ID when created. This ID is used when making API calls to specify which application you’re working with.
Format: app_xxxxxxxxxxxxxxxx
Example: app_abc123xyz456def
You’ll need this ID when:
- Creating templates via API
- Generating templates for specific applications
- Retrieving application details via API
💡 Tip: You can find your Application ID in the application details page or in the API response when retrieving applications.
Need Help?
Section titled “Need Help?”If you have questions about applications or need assistance:
- 📧 Email: support@docstron.com
- 💬 Live Chat: Available in your dashboard
- 📚 Documentation: You’re reading it!