Structure
Organizations to projects to issues
DevShip gives teams a clean hierarchy that scales from one client workspace to a multi-organization delivery operation.
Access control
Keep access intentional
Project-level assignment makes it easy to expose the right work to the right team members without opening everything to everyone.
Context
Each project gets its own identity
Unique slugs, project-scoped tags, and optional GitHub linking make each project feel purposeful instead of generic.
Why it matters
Less noise, better ownership.
When every issue belongs to a specific project, teams get cleaner boards, better reporting, and more accurate reference codes. Projects stop being labels and start acting like true work containers.
That separation also makes collaboration safer. Developers only need access to the projects they touch. Clients only see the portals tied to their organization. Managers still keep the broader picture.
And because project data inherits the team and organization hierarchy, the structure stays consistent across billing, reporting, tags, and future API usage.
Acme Corp
Client Portal v2
Slug: client-portal-v2 • 11 active issues
Reporting API
Slug: reporting-api • GitHub linked • 7 active issues
Internal Ops
Infrastructure
Slug: infrastructure • Restricted access • 3 active issues
Project-specific tags
Let each project define its own vocabulary without forcing one global tagging system across unrelated workstreams.
GitHub repository links
Connect a repository to a project so issue work and recent commits live closer together for engineering teams.
Scoped membership
Restrict sensitive projects while still keeping broader workspace collaboration simple for admins and managers.
Go deeper
See how slugs, permissions, and project structure work.
The docs explain project slugs, access control, GitHub integration, project-scoped tags, and issue code generation.
