# Slash output "Only visible to you" **URL:** \ **Category:** Troubleshooting\ **Created:** [February 26, 2020, 7:22pm UTC](https://forum.mattermost.com/t/slash-output-only-visible-to-you/9055 "2020-02-26T19:22:47Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![bobby789](https://avatars.discourse-cdn.com/v4/letter/b/ed655f/32.png) [@bobby789](https://forum.mattermost.com/u/bobby789)\ **Post date:** [February 26, 2020, 7:22pm UTC](https://forum.mattermost.com/t/slash-output-only-visible-to-you/9055/1 "2020-02-26T19:22:47Z")
Hey there, I wrote couple of simple slash commands, which trigger a web request to cloud, and return either a JSON object or plain text, which gets posted to a channel. Everything worked fine as expected, until something changed and now all of my slash commands display a message “(Only visible to you)”, which is not what I want. So the commands used to generate output which would to be visible to everyone. I been using this guide to create my slash commands. [https://docs.mattermost.com/developer/slash-commands.html#custom-slash-command](https://docs.mattermost.com/developer/slash-commands.html#custom-slash-command) Anyone else experiencing this behavior ? ---
**Author:** ![ahmaddanial](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/ahmaddanial/32/2938_2.png) [@ahmaddanial](https://forum.mattermost.com/u/ahmaddanial)\ **Post date:** [March 9, 2020, 6:36am UTC](https://forum.mattermost.com/t/slash-output-only-visible-to-you/9055/2 "2020-03-09T06:36:55Z")
Hi, @bobby789 Since you mentioned that it was working fine earlier and something changed, may I know if you made any recent changes to the slash command configuration / external application you wrote based on the [Custom Slash Command](https://docs.mattermost.com/developer/slash-commands.html#custom-slash-command) steps? How about Mattermost server upgrade? Can you share some examples here so I can get an overview of slash commands you have created? ---
**Author:** ![etlweather](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/etlweather/32/6610_2.png) [@etlweather](https://forum.mattermost.com/u/etlweather)\ **Post date:** [March 24, 2023, 3:45am UTC](https://forum.mattermost.com/t/slash-output-only-visible-to-you/9055/3 "2023-03-24T03:45:57Z")
@bobby789 Were you able to resolve that ---
**Author:** ![agriesser](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/agriesser/32/5644_2.png) [@agriesser](https://forum.mattermost.com/u/agriesser)\ **Post date:** [March 24, 2023, 4:38am UTC](https://forum.mattermost.com/t/slash-output-only-visible-to-you/9055/4 "2023-03-24T04:38:25Z")
Hi @etlweather and welcome to the Mattermost forums! I think this might be related to the fact that your external services’s response does not specify the `response_type` as explained by the documentation: > **[Custom commands](https://developers.mattermost.com/integrate/slash-commands/custom/#response-parameters)** > > Your one-stop shop for all of your Mattermost contribution, integration, and extension needs. It defaults to `ephemeral` which means that the message will only be visible to the one who issued the slash command, but you can change it to `in_channel` in order for the message to appear for everyone in the channel. ---
**Author:** ![etlweather](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/etlweather/32/6610_2.png) [@etlweather](https://forum.mattermost.com/u/etlweather)\ **Post date:** [March 24, 2023, 4:56am UTC](https://forum.mattermost.com/t/slash-output-only-visible-to-you/9055/5 "2023-03-24T04:56:12Z")
Ah, thanks. I went through the documentation but somehow missed that. In this case, it’s integration with GitLab (on-premise). I don’t see a way to change that unfortunately. Maybe if I upgrade GitLab (I am a few version behind still). ---
**Author:** ![agriesser](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/agriesser/32/5644_2.png) [@agriesser](https://forum.mattermost.com/u/agriesser)\ **Post date:** [March 24, 2023, 5:08am UTC](https://forum.mattermost.com/t/slash-output-only-visible-to-you/9055/6 "2023-03-24T05:08:52Z")
What’s the target of your slash command? What script from Gitlab is being called? ---
**Author:** ![etlweather](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/etlweather/32/6610_2.png) [@etlweather](https://forum.mattermost.com/u/etlweather)\ **Post date:** [March 24, 2023, 6:17am UTC](https://forum.mattermost.com/t/slash-output-only-visible-to-you/9055/7 "2023-03-24T06:17:38Z")
`/api/v4/projects/___/services/mattermost_slash_commands/trigger` I don’t know what script in GitLab is being called. It’s the GitLab Mattermost integration service thing. ---
**Author:** ![agriesser](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/agriesser/32/5644_2.png) [@agriesser](https://forum.mattermost.com/u/agriesser)\ **Post date:** [March 24, 2023, 6:33am UTC](https://forum.mattermost.com/t/slash-output-only-visible-to-you/9055/8 "2023-03-24T06:33:16Z")
OK, I can see it. Not sure if it’s possible to modify them, I think you would have to ask in a GitLab forum if it’s possible to modify the response of this command. I cannot see if the default behaviour has changed in Mattermost or in Gitlab, not sure if it’s easy to find out. ---
**Author:** ![etlweather](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/etlweather/32/6610_2.png) [@etlweather](https://forum.mattermost.com/u/etlweather)\ **Post date:** [March 24, 2023, 7:09am UTC](https://forum.mattermost.com/t/slash-output-only-visible-to-you/9055/9 "2023-03-24T07:09:05Z")
OK. Well thanks for your help, at least I understand what is happening. I’ll check the GitLab forum / issue tracker. ---
**Author:** ![agriesser](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/agriesser/32/5644_2.png) [@agriesser](https://forum.mattermost.com/u/agriesser)\ **Post date:** [March 25, 2023, 5:33am UTC](https://forum.mattermost.com/t/slash-output-only-visible-to-you/9055/10 "2023-03-25T05:33:40Z")
Alright, good luck with that and let us know if you found out if that’s configurable on GitLab’s end.