A screenshot can show the appearance of a project. It cannot tell a reader who planned the structure, wrote the copy, configured the tools, tested the site, or maintained it afterward.
A useful case study makes those roles explicit. Begin with the challenge and audience. Describe the part you owned, the collaborators involved, and the choices that shaped the result. If the project is still evolving, say so. If the numbers are not available, explain what the work enables rather than inventing a metric.
Permission matters too. A public site may be linkable while its admin screens, customer records and internal discussions remain private. A portfolio can show a simplified diagram or approved screenshot without exposing information that was never meant for the public.
That is how I intend to present my work here: specific enough to be useful, clear about my contribution, and respectful of the people and organizations behind it.