This guide provides an overview of PMKIN's data model, helping you understand how your content is organized and accessed.
PMKIN's data model is structured hierarchically, with Teams at the top, then Projects, and then Documents and Categories within each project.
Teams form the top level of the PMKIN hierarchy. This is where you invite team members to collaborate on content. Each team can contain multiple projects, allowing you to organize your work effectively.
Projects belong to a team and serve as isolated workspaces. Each project is accessible with its unique API key, ensuring that resources cannot be accessed between different projects. When you work with the PMKIN API, you are always scoped to a specific project.
Within each project, you'll find three main components: Documents, Categories, and API Keys.
Documents are your primary content items, such as blog posts or articles. Categories help you organize these documents into logical groups. API Keys are used to programmatically access the project's content, allowing you to integrate PMKIN with your applications.
This structure allows for efficient content management and seamless integration with your applications through the API while maintaining clear boundaries between different projects and teams.