Note in the API tenant visibility doc
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description
The tenant visibilty doc, there should be at least a note stating that the API visible to other tenants will only be in that tenant and the user of another tenant will need to switch to the API's tenant
Steps to Reproduce
Version
4.5.0
Environment Details (with versions)
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the linked tenant visibility documentation and find the section on controlling subscription availability in the developer portal. Add a note explaining that an API made visible to other tenants remains in its own tenant and that users from another tenant must switch to that tenant to access it. Done means the note clearly documents this tenant-switching requirement.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 62/100